Remove support for Composer v1 during CI #67
Merged
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
Member
Author
|
We have an issue with Scrutinizer which is trying to user composer v1… I ask the support because I don't know how to change that… |
jaylinski
approved these changes
Sep 25, 2025
Member
jaylinski
left a comment
jaylinski
left a comment
There was a problem hiding this comment.
👍 Maybe we should drop unsupported PHP versions (and add PHP 8.4) in one of our next releases to reduce the amount of PHP versions in our CI pipeline.
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.
Since the Composer v1 shutdown announce we needed to move away from Composer v1.
Now the deadline has been reached: https://blog.packagist.com/shutting-down-packagist-org-support-for-composer-1-x/#key-dates
I chose to drop the composer v1 from the CI.