Support updateLockedDependency() for Yarn 2+

[rarkins]

What would you like Renovate to be able to do?

Support updateLockedDependency() gracefully for Yarn 2+.

Currently it results in quite ungraceful "Unexpected depNameConstraint" debug messages like:

{"level":20,"branch":"renovate/plasmicapp-react-web-0.x-lockfile","msg":"npm.updateLockedDependency: @plasmicapp/react-web@0.2.104 -> 0.2.205 [yarn.lock]","time":"2023-05-01T19:30:06.491Z"}
{"level":20,"branch":"renovate/plasmicapp-react-web-0.x-lockfile","depNameConstraint":"__metadata","entry":{"version":"6","cacheKey":"8"},"msg":"Unexpected depNameConstraint","time":"2023-05-01T19:30:06.580Z"}

If you have any ideas on how this should be implemented, please tell us here.

We do not need to be able to actually update the locked dependency, but we should be able to gracefully detect if it's already updated.

Today our getLockedDependencies() function is called prior to us checking if it's Yarn 2. It's probably best that we can gracefully parse that.

Is this a feature you are interested in implementing yourself?

No

[renovate-release]

🎉 This issue has been resolved in version 35.86.0 🎉

The release is available on:

• GitHub release
• 35.86.0

Your semantic-release bot 📦🚀