-
Notifications
You must be signed in to change notification settings - Fork 241
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.
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
PHPUnit 10 compatibility, master is compatible but not the v1.17.0 tag… #599
Comments
Not a maintainer of this project but think at current case the best until it is released is what we can do, is to test if the current "require-dev": {
"phpspec/prophecy": "^1.18@dev",
"phpspec/prophecy-phpunit": "^2.1@dev",
"phpunit/phpunit": "^10.2"
} For paratest user also update to: "brianium/paratest": "^7.0", is required. In my case with a project about ~1800 Unit Tests using prophecy all did work fine. |
@stof , I think it was you releasing last time. You think a new release of what is already merged is possible? |
Any updates on this? I really dislike using @dev's in my composer.json... |
+1 |
Hello @stof. Do you need any help releasing a new version? |
1.18.0 has been released now |
thanks @stof ! Unfortunately, I failed to install it because this one is not yet compatible (yet having v10 PR already merged, simply not released): |
Hello !
I work on a project where we are using both PHPUnit and PHPSpec. I can't upgrade to PHPUnit 10 because there is a conflict with the latest stable version of phpspec/prophecy which requires sebastian/recursion-context v4.
I viewed that the master branch is up to date and allows installing PHPUnit 10, do you think it might be possible to create a new release ? Is there some instability today on master that might block the release process ?
If so I can try to help fixing those issues… Let me know 😄
The text was updated successfully, but these errors were encountered: