pnpm 7 can not update lockfile #15416
-
How are you running Renovate?WhiteSource Renovate hosted app on github.com If you're self-hosting Renovate, tell us what version of Renovate you run.No response Please select which platform you are using if self-hosting.No response If you're self-hosting Renovate, tell us what version of the platform you run.No response Was this something which used to work for you, and then stopped?It used to work, and then stopped Describe the bugWhen pnpm v7 come, renovate can not update lockfile, and just update package.json. so in CI mode can not do pnpm i, because lockfile is not updated. And in every PRs, renovate bot will leave a comment. ⚠ Artifact update problem ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: any of the package files in this branch needs updating, or File name: pnpm-lock.yaml Link there: mx-space/core#473 Relevant debug logsLogs
Have you created a minimal reproduction repository?No reproduction, but I have linked to a public repo where it occurs |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
This comment has been hidden.
This comment has been hidden.
-
There's a good chance this is a peer dependency failure behind the scenes. Check the stdout of the pnpm command in the debug logs |
Beta Was this translation helpful? Give feedback.
-
same issue as: |
Beta Was this translation helpful? Give feedback.
-
new node docker images are pushed, so now it show the real error on next (forced) run |
Beta Was this translation helpful? Give feedback.
-
If you want to stay on pnpm v6 and take some time to upgrade you could add this to your "constraints": {
"pnpm": "6"
}, I just did that and from debug logs it resolves correctly to latest v6 after, which fixes the problem until we upgrade to v7 and remove this.
See https://docs.renovatebot.com/configuration-options/#constraints |
Beta Was this translation helpful? Give feedback.
There's a good chance this is a peer dependency failure behind the scenes. Check the stdout of the pnpm command in the debug logs