Description
Copying a bug report from @sergioflores-j for tracking:
- Catalogs Tracking Issue #7072 (comment)
- https://github.com/sergioflores-j/pnpm-bugs-repro?tab=readme-ov-file#1-specifier-changes-but-resolved-version-is-still-the-same
Text below is from @sergioflores-j:
Verify latest release
- I verified that the issue exists in the latest pnpm release
Which area(s) of pnpm are affected? (leave empty if unsure)
Dependencies resolver, CLI, Lockfile
Link to the code that reproduces this issue or a replay of the bug
Reproduction steps
- Set in .npmrc
recursive-install=false - Change a version in
pnpm-workspace.yaml(e.g. typescript) - Run either
pnpm i --lockfile-onlyorpnpm ifrom the root of the repository
Describe the Bug
Only the specifier of the catalog dependency gets changed but the resolved version is still the old one.
Secondary behavior
If running pnpm i from a package (e.g. inside the directory packages/package-a). Only that packages starts resolving the new version and the catalog still refers to the old one.
Expected Behavior
That the resolved version for all packages gets updated. Like when using recursive-install=true instead.
IMHO as the catalog is a centralized configuration, all packages should be updated independently of the recursive-install setting.