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
Missing upper constraint for PHP version #141
Comments
No, it shouldn't be changed. PHP doesn't follow semver and restricting the runtime upper bound is nonsense. |
Well then, looking forward to using this library with PHP in a few years. ;-) |
If you restrict this at all, the restriction would need to be Also, one can't just pull a new php version via composer. Composer can always pull an older version of a library dependency though. It's the responsibility of the run-time to be as forward compatible and as less breaking as possible, between every version. |
@bwoebi You are absolutely right, i should have phrased it like that. This way it becomes clear what PHP versions this library has been tested against and is guaranteed to work with. |
@mathbr Sorry for being a bit harsh. We would maybe decide differently if PHP was pulled via Composer, but with the current way of working, |
@kelunik No worries, I'm not offended. ;-) You are the maintainer, thus it's your choice. |
Currently the
composer.json
contains this:This promises that this library is compatible to any future PHP version (e.g. 8, 9, etc.) for all eternity.
Realistically speaking this is impossible thus this should be changed:
The text was updated successfully, but these errors were encountered: