Failed composer update/require still results in packages marked as "linked" #81

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.

Sign up for GitHub

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

Jump to bottom

Open

timkelty opened this issue Apr 16, 2025 · 0 comments

Labels

bug

timkelty commented Apr 16, 2025

Example:

❯ composer link "packages/craftcms/cms"
Linking packages, Lock file will be generated in memory but not written to disk.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
[truncated error explanation]
Linking packages finished!

❯ composer linked
craftcms/cms	packages/craftcms/cms

Shows as linked, even though it isn't because it failed.

The text was updated successfully, but these errors were encountered:

SanderSander added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment