feat: add option skipArtifactsUpdate

[reduckted]

Changes

This adds a new option called skipArtifactsUpdate. When set to true, artifact updating will be skipped.

This new option replaces the existing updateLockFiles option. A migration will replace updateLockFiles=false with skipArtifactsUpdate=true.

Context

• Closes New option: skipArtifactUpdating #33118

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[reduckted]

Is there anything else needed for this to be merged?

[rarkins]

@RahulGautamSingh @viceice have either of you had the chance to test this on some real examples? This has the chance to break a lot of people if it has a bug

[RahulGautamSingh]

I will test tonight +5.30 GMT

[RahulGautamSingh]

Tested

[RahulGautamSingh]

Note:

When user disable artifact updates they will involuntarily receive wrong updates for the packageManager field in their package.json files if the version string contains a hash as we trigger corepack update in the updateArtifacts function for the npm manager module.

Example:

packageManager: "pnpm@1.2.0" this will get updated correctly ✅

packageManager: "yarn@3.0.0+sha224.deadbeef" this will get updated to "yarn@3.1.0" ❌

[rarkins]

Please add that warning to the docs

[reduckted]

Anything else needed?

[renovate-release]

🎉 This PR is included in version 41.62.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 41.62.0

Your semantic-release bot 📦🚀