Normalize accidentally widened php constraint #46
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This component was released with an accidentally widened PHP constraint back in August 2020 due to myself introducing PHP 8.0 support.
With PHP 8.1, I also added
~8.1.0(which was unnecessary at this point, I have no idea why I didn't realized it back then...) as in laminas/mezzio/laminas-api-tools components, we do use more strict PHP constraints to avoid surprises with new PHP releases.As of now, this component would be installable on PHP 8.2 while it was never tested with that version. Since we do not want to provide implicit support for PHP 8.2, changing the PHP constraint to
~7.4.0 || ~8.0.0 || ~8.1.0will do the trick.Closes #45