GH Actions: run integration tests against Composer snapshot #163
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
... for a limited set of builds to get early warning of upcoming changes we need to be aware of. It has already been announced that Composer 2.3 will drop support for PHP < 7.2 and there may be more breaking changes, so seeing test failures early would seem a good thing (both to fix things in the plugin, if needs be, as well as to report issues with the next version of Composer upstream).
Potherca
approved these changes
Mar 5, 2022
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.
Proposed Changes
Run integration tests against Composer snapshot for a limited set of builds to get early warning of upcoming changes we need to be aware of.
It has already been announced that Composer 2.3 will drop support for PHP < 7.2 and there may be more breaking changes, so seeing test failures early would seem a good thing (both to fix things in the plugin, if needs be, as well as to report issues with the next version of Composer upstream).