-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update composer/composer version constraint to support Composer 2 #3
Conversation
Looking at it, I'm not sure this repo needs a composer version constraint at all. What do you think? |
For the API compatibility, I think it's good to have a version set in. But it doesn't has to be As far as I remember, older PHP versions didn't care if the traits match the interface, but recent versions do. So if composer were to introduce a new version with API changes, this trait will break backwards compatibility. So I think it's good to have a version locked it just to be sure. |
to use composer-patches with composer v2 - which was added with cweagans/composer-patches#309 - we would also need a new release of this package, with the merged changes. |
Hi, is there any news about tagging a new release? |
All PaaS upgraded their composer to version 2, hence the "emmergency" there :) @cweagans |
You should definitely not be using any version of composer patches that depends on this plugin. Use 1.7.0. |
Oh you're right, we were looking at master branch. |
1.x is the current stable release series and is on the 1.x branch that split off from master a while back . Master is 2.x. :) |
Oh alright. Thanks for you explanation! :) |
Updates the
composer.json
scomposer/composer
version to allow composer v2 as well.Related to cweagans/composer-patches#309.
Thank you.