Add support for Composer version 2 #321
Conversation
Cherry picking from #309
| "packages": [], | ||
| "packages-dev": [ | ||
| { | ||
| "name": "composer/ca-bundle", |
There was a problem hiding this comment.
This looks like a lot of unrelated changes got caught in the cherry-pick.
I think you should revert the composer.lock file to 972fac4 then run composer update --lock.
There was a problem hiding this comment.
I was wondering about that. Is there a reason there is a composer.lock. It typically isn't in version control for libraries. It doesn't get used anyway when requiring a package.
There was a problem hiding this comment.
And these changes might be because I also changed the version constraint for composer/composer to "^1.0 || ^2.0". That has introduced new packages.
There was a problem hiding this comment.
Oh right, I didn't see you changed the composer/composer dev requirement.
That would indeed explain it.
|
I am doing my own testing and bumping issues, like this one: composer/composer#9079 |
5 participants
Cherry picking from #309