pnpm lock file not updating after v7 release

[privatenumber]

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 bug

Previously, the pnpm-lock.yaml file used to get updated in the Renovate PRs:
https://github.com/privatenumber/minification-benchmarks/pull/142/files

Since pnpm v7 got released, it stopped:
https://github.com/privatenumber/minification-benchmarks/pull/144/files

Relevant debug logs

No response

Have you created a minimal reproduction repository?

No reproduction, but I have linked to a public repo where it occurs

[viceice]

It's a pnpm change

privatenumber/minification-benchmarks#144 (comment)

[viceice]

Breaking change of pnpm v7

• https://github.com/pnpm/pnpm/releases/tag/v7.0.0
• feat: strict-peer-dependencies is true by default pnpm/pnpm#4427

[privatenumber]

My bad. I thought I had corrected this and assumed it was an outdated comment. I just realized it gets updated!

Locally, I was getting a list of unmet peer dependencies where only one of them (dayjs) was an failure (x), and the rest (in the screenshot above) were all warnings. So after adding dayjs to the ignore list, it wasn't failing for me on reinstalls.

However, I was able to reproduce this by deleting pnpm-lock.yaml and running pnpm i again. I was able to fix it and now Renovate updates the pnpm file!

Thanks for your help!

[viceice]

Duplicate of

• Renovate can't update pnpm-lock.yaml when there's a peer dependencies error #15410
• pnpm 7 can not update lockfile #15416

[Jolg42]

If you want to stay on pnpm v6 and take some time to upgrade you could add this to your renovate.json

  "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.

DEBUG: Resolved version(branch="renovate/dependencies-(non-major)")
{
  "toolName": "pnpm",
  "constraint": "6",
  "resolvedVersion": "6.32.11"
}

See https://docs.renovatebot.com/configuration-options/#constraints

[privatenumber]

Trying to upgrade to v7 but thanks for the tip!

[privatenumber]

For anyone else reading, the peer dependency error can be silenced with a .npmrc file with strict-peer-dependencies=false if they're not fixable.