Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Any reason to insist on Codeception 2.0.0 #6

Closed
pablopaul opened this issue Sep 24, 2014 · 4 comments · Fixed by #7
Closed

Any reason to insist on Codeception 2.0.0 #6

pablopaul opened this issue Sep 24, 2014 · 4 comments · Fixed by #7

Comments

@pablopaul
Copy link
Contributor

Hi,

is there any specific reason to insist on Codeception version 2.0.0? Maybe we could move forward to actual on (2.0.5): https://github.com/allure-framework/allure-codeception/blob/master/composer.json#L20
@vania-pooh
Copy link
Contributor

@pablopaul I could change to ~2.0.0.

pablopaul added a commit to pablopaul/allure-codeception that referenced this issue Sep 24, 2014
@pablopaul
Require any Codeception release in 2.0.x branch
3878e38 
Require any Codeception release in 2.0.x branch instead of exact 2.0.0 version.
Fix allure-framework#6.
@pablopaul pablopaul mentioned this issue Sep 24, 2014
Merged
@pablopaul
Copy link
Contributor Author

@vania-pooh sounds good, please find attached PR.

@vania-pooh
Copy link
Contributor

Done.

@vania-pooh
Copy link
Contributor

Also see https://github.com/allure-framework/allure-codeception/releases/tag/1.1.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Require any Codeception release in 2.0.x branch pablopaul/allure-codeception
2 participants
@pablopaul @vania-pooh