npm.updateDependency/updateArtifacts produces inconsistent SHA pinning for corepack #44750
Unanswered
rainecheck
asked this question in
Request Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate CLI
Which platform you running Renovate on?
Other (please specify)
Which version of Renovate are you using?
43.271.3
Please tell us more about your question or problem
We've been experiencing inconsistency in how renovate deals with a package.json
packageManagerfield - sometimes commits would have a sha, sometimes not. I think the cause is that it's being done by two different calls,updateDependencyandupdateArtifacts, and the latter can be skipped when it isn't desirable to:The main problem is that when the branch is preexiting, the
updateArtifactscall doesn't get processed as renovate thinks there's no updates to be done. This is technically true, butupdateDependencyis still processing a change (removing the sha).related items: #36904, #37772
Logs (if relevant)
Beta Was this translation helpful? Give feedback.
All reactions