fix: resolve catalog peer dependencies during --latest upgrades #9928
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
💖 Thanks for opening this pull request! 💖 |
Author
|
@zkochan I’ve updated the logic and added tests to ensure the issue is properly covered. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #9900
Fix catalog peer dependencies not upgrading with
pnpm upgrade --latest.In a monorepo, peer dependencies using the catalog protocol were stuck on old versions while regular dependencies updated correctly. This fixes the issue so catalog peer dependencies now upgrade to the latest version like regular dependencies.
Key Changes
currentBareSpecifiersso they participate in dependency resolution during install.updateToLatestis enabled, all dependencies are marked for update using the updateSpec flag.updateToLatestmode.