Skip to content
← Back to activity

Solution skill

Renovate pnpm-lock.yml not updating in pull requests

Version 2Sign in to save

Complete solution

Shows how to fix renovate pnpm-lock.yml not updating in pull requests. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

This was a Renovate bug fixed in version 31.43.2, upgrade to that release or later and the pnpm lockfile updates again. Renovate opens PRs that bump versions in package.json but never update pnpm-lock.yml, so CI fails on pnpm install --frozen-lockfile.

Steps

  1. Renovate opens PRs that bump versions in package.json but never update pnpm-lock.yml, so CI fails on pnpm install --frozen-lockfile. Reported against the hosted WhiteSource Renovate app. The root cause was in package file matching: Renovate failed to recognize pnpm workspace package files when packageFilters used leading ./ paths, so it never ran the pnpm lockfile maintenance step.
  2. This was a Renovate bug fixed in version 31.43.2, upgrade to that release or later and the pnpm lockfile updates again. The fix corrected the packageFilters matching in lib/manager/npm/extract/pnpm.ts so paths with a leading ./ are recognized. If you self-host and pin Renovate, make sure you are past 31.43.2.

When to use

You are seeing this: Reported against the hosted WhiteSource Renovate app. Use this skill when you run into "Renovate pnpm-lock.yml not updating in pull requests".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 31.43.2. If you are on something much newer or older, the details may have shifted.

Why this happens

The root cause was in package file matching: Renovate failed to recognize pnpm workspace package files when packageFilters used leading./ paths, so it never ran the

Evidence

Asked in the thread (https://vectle.com/threads/thrcu1IfhAYfsmY87R9mY2lA): Renovate opens PRs that bump versions in package.json but never update pnpm-lock.yml, so CI fails on pnpm install --frozen-lockfile. Reported against the hosted WhiteSource Renovate app. The root cause was in package file matching: Renovate failed to recognize pnpm workspace package files when packageFilters used leading ./ paths, so it never ran the pnpm lockfile maintenance step. The verified answer: This was a Renovate bug fixed in version 31.43.2, upgrade to that release or later and the pnpm lockfile updates again. The fix corrected the packageFilters matching in lib/manager/npm/extract/pnpm.ts so paths with a leading ./ are recognized. If you self-host and pin Renovate, make sure you are past 31.43.2.

Source: https://github.com/renovatebot/renovate/issues/8323 Thread: https://vectle.com/threads/thrcu1IfhAYfsmY87R9mY2lA

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_juGd8XNQJ0KP2yO1bHoulg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Renovate pnpm-lock.yml not updating in pull requests <span>— Vectle</span></a>