-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Composer 2.2+ breaks composer update <package>
in monorepos
#10431
Comments
I think that Path Repositories should handle both |
This does not seem to have anything to do with dev-master versus dev-main. |
@anomiex thanks for the great reproducer. This helped a lot. And indeed it was related to the dev-main alias. You can try with |
Seems to work so far! If I run into more problems, I'll let you know. Thanks for the quick response! |
In a monorepo where package C depends on B which depends on A, and C has a lockfile, trying to do a
composer update <package>
in C will fail due to Composer not "loading" A at all. This seems to have been caused by #10157.Note that in the example given below, nothing is being changed by the
composer update
. You may also want to have a look at renovatebot/renovate#13371, in which some things actually are being changed.My
composer.json
:test.zip
Output of
composer diagnose
:When I run this command:
I get the following output:
Output
Note that specifying
--with-all-dependencies
makes no difference.And I expected this to happen:
Output
Or, if
composer install
had been run previously,Output
The text was updated successfully, but these errors were encountered: