Yarn Zero-Installs stopped working (lockfile maintenance)

[MGough]

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 has stopped committing files from .yarn during the lockfile update. We were seeing this working on the 21st of October but our more recent lockfile updates have been missing the files from .yarn leading to a broken build (our CI blocks if dependencies are added during the run as they should already be present).

There have been minor changes to our renovate config in this time, but these were around adding python, and moving the schedule of lockfile maintenance earlier in the day due to some slow CI on our side. This is our configuration:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:js-app",
    ":semanticCommitType(chore)",
    ":semanticCommitTypeAll(chore)",
    ":preserveSemverRanges",
    ":enablePreCommit",
    ":enableVulnerabilityAlertsWithLabel(vulnerability)"
  ],
  "timezone": "Europe/London",
  "constraints": {
    "python": "==3.10"
  },
  "python": {
    "enabled": true
  },
  "lockFileMaintenance": {
    "enabled": true,
    "automerge": true,
    "schedule": ["before 1am on monday"]
  },
  "schedule": ["on the 1st and 3rd day instance on sunday after 7pm"],
  "minimumReleaseAge": "3 days",
  "packageRules": [
    {
      "matchDatasources": ["npm"],
      "schedule": [
        "after 10pm every weekday",
        "before 5am every weekday",
        "every weekend"
      ],
      "automergeSchedule": [
        "after 10pm every weekday",
        "before 5am every weekday",
        "every weekend"
      ],
      "groupName": "all patch dependencies (yarn)",
      "groupSlug": "all-patch-yarn",
      "matchPackagePatterns": ["*"],
      "matchUpdateTypes": ["patch"],
      "matchCurrentVersion": "!/^0/",
      "automerge": true
    },
    {
      "matchDatasources": ["cargo"],
      "schedule": [
        "after 10pm every weekday",
        "before 5am every weekday",
        "every weekend"
      ],
      "automergeSchedule": [
        "after 10pm every weekday",
        "before 5am every weekday",
        "every weekend"
      ],
      "groupName": "all patch dependencies (cargo)",
      "groupSlug": "all-patch-cargo",
      "matchPackagePatterns": ["*"],
      "matchUpdateTypes": ["patch"],
      "matchCurrentVersion": "!/^0/",
      "automerge": true
    },
    {
      "matchDatasources": ["python"],
      "schedule": [
        "after 10pm every weekday",
        "before 5am every weekday",
        "every weekend"
      ],
      "automergeSchedule": [
        "after 10pm every weekday",
        "before 5am every weekday",
        "every weekend"
      ],
      "groupName": "all patch dependencies (python)",
      "groupSlug": "all-patch-python",
      "matchPackagePatterns": ["*"],
      "matchUpdateTypes": ["patch"],
      "matchCurrentVersion": "!/^0/",
      "automerge": true
    }
  ]
}

It looks like from the logs below that it's aware of .yarn/cache but isn't seeing files there?

Logs (if relevant)

Logs

DEBUG: Executing command (branch="renovate/lock-file-maintenance")
{
  "command": "yarn install --mode=update-lockfile"
}

DEBUG: exec completed (branch="renovate/lock-file-maintenance")
{
  "durationMs": 303796
  "stdout": "➤ YN0000: · Yarn 4.5.1\n➤ YN0000: ┌ Resolution step\n➤ YN0000: ┌ Link step\n➤ YN0073: │ Skipped due to mode=update-lockfile\n➤ YN0000: └ Completed\n➤ YN0000: · Done with warnings in 5m 2s\n"
  "stderr": "! Corepack is about to download https://repo.yarnpkg.com/4.5.1/packages/yarnpkg-cli/bin/yarn.js\n"
}

DEBUG: yarn.lock needs updating (branch="renovate/lock-file-maintenance")
DEBUG: updateYarnOffline resolvedPaths (branch="renovate/lock-file-maintenance")
{
  "resolvedPaths": [
    ".yarn/cache",
    ".pnp.cjs",
    ".pnp.js",
    ".pnp.loader.mjs"
  ]
}

DEBUG: Updated 4 lock files (branch="renovate/lock-file-maintenance")
{
  "updatedArtifacts": [
    "packages/desktop/python-backend/poetry.lock",
    "packages/desktop/src-tauri/Cargo.lock",
    "packages/desktop/src-tauri/Cargo.lock",
    "yarn.lock"
  ]
}

DEBUG: 3 file(s) to commit (branch="renovate/lock-file-maintenance")
DEBUG: Preparing files for committing to branch renovate/lock-file-maintenance (branch="renovate/lock-file-maintenance")
DEBUG: Setting git author name: renovate[bot] (branch="renovate/lock-file-maintenance")
DEBUG: Setting git author email: 29139614+renovate[bot]@users.noreply.github.com (branch="renovate/lock-file-maintenance")
DEBUG: git commit (branch="renovate/lock-file-maintenance")
{
  "deletedFiles": []
  "ignoredFiles": []
  "result": {
    "author": null,
    "branch": "renovate/lock-file-maintenance",
    "commit": "704d7616a97157b6e7375457551d754df2f212e5",
    "root": false,
    "summary": {
      "changes": 3,
      "insertions": 1429,
      "deletions": 1384
    }
  }
}

[github-actions[bot]]

Hi there,

Get your discussion fixed faster 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