Override default pnpm install command

[unknownbanana]

How are you running Renovate?

Self-hosted Renovate

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

Platform: Kubernetes
Renovate: 39.62.6

Please tell us more about your question or problem

We are running a NX monorepo with a single package.json and pnpm-lock.yaml at the root of the repository.
Each project in the monorepo has a package.json file containing the dependencies on other projects in the repository.
These dependencies are not stored in any artifact repository because the projects are present in the same repository.

When Renovate attempts to update the package.json and the pnpm-lock.yaml file at the root of the repository it fails because it attempts to execute a pnpm install --recursive, which causes pnpm to lookup all package.json files in the monorepo. Even the ones that do not contain dependencies that can be retrieved from an artifact repository.

This results in a failure when running renovate for npm/pnpm dependencies in our monorepo, since pnpm cannot retrieve some dependencies and exits the moment it attempts to do so.

Regarding a solution. One, I believe that NX is abusing the package.json of a project to add dependencies which cannot be retrieved from a remote source, which is the express purpose of a package.json file.
Two, I believe that renovate should have the functionality such that I can tweak the pnpm install command to my liking, regardless of the reason I wish to do so.

Hence I would like to ask whether renovate has a feature that allows me to run a random command on a repository, rather than a specific command and if not, whether there is a feature that allows me to override the command used to install packages using pnpm.

Another way to achieve the same goal would be to allow a user to filter the projects where pnpm should run an install using a --filter.

Logs (if relevant)

Note that I have added a packageRules property to the renovate.json file in the repository that looks like this:

  "packageRules": [
    {
      "matchPackageNames": ["@group/**"],
      "enabled": false
    }
  ]

Logs

I have omitted the options property, as they contain references to my employer and they're irrelevant to the issue.
Names and identifiers that can track this issue to my employer but are relevant have been replaced.

DEBUG: lock file error (repository=project/repo, branch=renovate/all-minor-patch)
       "commands": ["pnpm install --recursive --lockfile-only --ignore-scripts --ignore-pnpmfile"],
       "err": {
         "cmd": "/bin/sh -c pnpm install --recursive --lockfile-only --ignore-scripts --ignore-pnpmfile",
         "stderr": "",
         "stdout": "Scope: all 28 projects\nProgress: resolved 1, reused 0, downloaded 0, added 0\n.                                        |  WARN  deprecated eslint@8.57.1\nProgress: resolved 35, reused 0, downloaded 0, added 0\nProgress: resolved 58, reused 0, downloaded 0, added 0\nundefined\n/tmp/renovate/repos/bitbucket-server/project/repo/path/project:\n ERR_PNPM_FETCH_404  GET https://**redacted**@group%2Fapplication-name: Not Found - 404\n\nThis error happened while installing a direct dependency of /tmp/renovate/repos/bitbucket-server/project/repo/path/project\n\n @group/application-name is not in the npm registry, or you have no permission to fetch it.\n\nNo authorization header was set for the request.\nundefined\nundefined\n",
       },
       "stdout": undefined,
       "stderr": undefined,
       "type": "pnpm"

[rarkins]

I have created this feature request: #33118

It's purpose is to allow the disabling of Renovate's default artifact updating. After that you could use postUpgradeTasks to run whatever you want.

[unknownbanana]

Thanks @rarkins , I was on holiday for a bit, hence the late reply.