Closed alpipego closed 2 years ago
OK with the fix you get this if it's a path repo package:
- Root composer.json requires foo/bar ^1.0.0, found foo/bar[2.0.0] but it does not match your constraint and is therefore not installable. Make sure you fix the constraint as packages installed from symlinked path repos are updated even in partial updates and the one from the lock file can thus not be used.
And this otherwise (package in lock that you didn't mean to update, but actually was explicitly in the update allowlist)
- Root composer.json requires foo/bar ^1.0.0, found foo/bar[2.0.0] but it does not match your constraint and is therefore not installable. Make sure you either fix the constraint or avoid updating this package to keep the one present in the lock file (foo/bar[1.0.0]).
I hope this is clearer :)
A follow-up on this tweet: https://twitter.com/naderman/status/1480827546052739077
My
composer.json
:Output of
composer diagnose
:When I run this command:
I get the following output:
And I expected this to happen:
Ideally, it would only update the package specified in the update command (
johnpbloch/wordpress-core
) and not ones that don't share dependencies with the requested package. I understand that @naderman says this is due to the unbound versions/branches.The message is misleading, however:
Make sure you either fix the constraint or avoid updating this package to keep the one from the lock file.
The last part is what I'm doing, I'm trying to avoid updating this package. The message should somehow reflect that this is not possible in this case.I am aware that I can get rid of the message by changing the constraint for
alpipego/awp-rtacf
fromdev-master
todev-stable
.