ERROR Failed to switch pnpm to vXX. Looks like pnpm CLI is missing at ...

[FGoessler]

How are you running Renovate?

A Mend.io-hosted app

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

Renovate bot is not able to to properly update our dependencies anymore using pnpm. It opens the PR but then fails to update the artifacts. Leading to an updated package.json file, but not updating pnpm-lock.yaml.

The error we get is:

ERROR  Failed to switch pnpm to v9.15.8. Looks like pnpm CLI is missing at "/home/ubuntu/.local/share/pnpm/.tools/pnpm/9.15.8/bin" or is incorrect
spawnSync /home/ubuntu/.local/share/pnpm/.tools/pnpm/9.15.8/bin/pnpm ENOENT

In full this looks like this on the PR:

It is additionally annoying as we use automerge and somehow renovate is ignoring this failure and merging the PR faster than our github actions manage to start. The comment about the failure to update artifacts and the merge happen within the same minute. => We get lots of actually failing dependency updates merged onto our main branch. 😞

Maybe this related to an issue in pnpm itself? Maybe this: pnpm/pnpm#9192 ?

We use the engines and packageManager fields in package.json:

{
  "dependencies": {
    // ...
  },
  "devDependencies": {
    // ...
  },
  "engines": {
    "node": ">=18.18",
    "pnpm": ">=9.14.4 <10"
  },
  "packageManager": "[email protected]+sha512.ed98f9c748442673c46964b70345bd2282c9b305e8eae539b34ab31d6ef24ef8dd59d8b55f27466f705500b009d9c113471cf87e544f3d5036b297330c26e996"
}

Logs (if relevant)

No response

[github-actions[bot]]

Hi there,

Please help this Discussion progress by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team