-
Notifications
You must be signed in to change notification settings - Fork 456
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
HHVM Fixes #270
HHVM Fixes #270
Conversation
All tests pass on every php version now. :P |
@@ -21,7 +21,8 @@ | |||
"lib-pcre": ">=7.0" | |||
}, | |||
"require-dev": { | |||
"hamcrest/hamcrest-php": "~1.1", | |||
"phpunit/phpunit": "4.0.*", | |||
"hamcrest/hamcrest-php": "1.1.*", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why tighten this requirement?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To make sure there are no unexpected changes. You can always raise the version when 1.2 is release, or I can revert this change if you like?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because it's a dev requirement, by keeping it loose, if they do break BC, we might catch it before one of our users catches it. Also, I think I'm a maintainer on that repo, so will be whinging at people if they break BC, if I have my way we'll stick to semver from now onwards.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. Sure. Check out my take 3?
I'll redo this pull... |
See #271. |
See #274. |
Let's load in phpunit 4.0. Let's make sure we only try to push to coveralls if we are not using hhvm.