fix: pin the Renovate version

[cryptodev-2s]

Explanation

Renovate pull requests opened today carry an artifact failure, #10369 for example:

error This project's package.json defines "packageManager": "yarn@4.17.1".
However the current global version of Yarn is 1.22.22.
Corepack must currently be enabled by running corepack enable in your terminal.

Renovate fell back to the Yarn 1 in its own image instead of resolving Yarn from packageManager, so the lockfile is not updated properly.

This is a known upstream bug, not our config. generateLockFile for Yarn chooses between Corepack and the Yarn 1 fallback using managerData.hasPackageManager, and that flag gets lost on some update shapes. Open since November 2023 as renovate#25853, with an unmerged fix in renovate#45153. One of our five failures, fast-xml-parser, is in the root resolutions block, which is exactly the case that PR describes.

What changed today is how often we hit it. renovatebot/github-action defaults renovate-version to the floating 44 tag, so pinning the action by SHA does nothing for the Renovate version inside it. From our own run logs:

Run	Renovate	Branches with PRs	Artifact failures
21 Sep 18:16	44.106.0	6	0
22 Sep 15:31	44.107.0	11	5

renovate/execa-10.x is the controlled case: it produced a correct lockfile on 44.106.0 and failed on 44.107.0.

So this pins renovate-version to 44.106.0. Treat it as a stopgap rather than a root cause fix. Nothing in the 44.107.0 changelog touches Yarn or Corepack, its six commits are all Helm, mise, docs and CI, so the trigger is more likely the rebuilt base image or cache state than Renovate source. If the failures come back on 44.106.0 we will know the pin was the wrong lever and the real answer is waiting on renovate#45153.

Deliberately no # renovate: annotation on the pin: nothing in CI exercises a Renovate run, so an automatic bump would put us back here without warning.

The already open pull requests need their rebase checkbox ticked afterwards to pick up a good lockfile.

References

Follows #10334. Part of WPC-1161.

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

[mcmire]

LGTM!