pnpm named catalogs misidentified as yarn.catalog, lockfile not updated #41731
Replies: 1 comment
-
|
Closing as this seems to be resolved since this morning: xballoy/renovate-pnpm-named-catalog-repro#4 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
A Mend.io-hosted app
Which platform you running Renovate on?
GitHub.com
Which version of Renovate are you using?
43.59.0
Please tell us more about your question or problem
When using pnpm named catalogs (not the default catalog) in
pnpm-workspace.yaml, Renovate updates the catalog version entry but does not regeneratepnpm-lock.yaml.This causes
pnpm install --frozen-lockfileto fail with:ERR_PNPM_LOCKFILE_CONFIG_MISMATCH Cannot proceed with the frozen installation.
The current "catalogs" configuration doesn't match the value found in the lockfile
The PR diff only contains changes to
pnpm-workspace.yamlandpnpm-lock.yamlis completely absent.Describe what you expected to happen instead
Renovate should regenerate
pnpm-lock.yamlwhen it modifies named catalog entries inpnpm-workspace.yaml, just as it does for regularpackage.jsondependency updates.Minimal reproduction
https://github.com/xballoy/renovate-pnpm-named-catalog-repro
The setup:
pnpm-workspace.yamlwith a named catalog (backend) containingtypescript: 5.0.2package.jsonreferencing"typescript": "catalog:backend"pnpm-lock.yamlgenerated and committedRenovate PR: xballoy/renovate-pnpm-named-catalog-repro#4
pnpm-workspace.yaml(typescript: 5.0.2→5.9.3)pnpm-lock.yamlLogs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions