Update packageManager hash #29184
Replies: 2 comments 5 replies
-
We should definitely add this. Is it possible that Renovate can determine the sha on its own without requiring to run If not, then is it ok for Renovate to partially update on its own like it does today (e.g. bump to |
Beta Was this translation helpful? Give feedback.
-
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. To get started, please read our guide on creating a minimal reproduction. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
-
Tell us more.
I recently learned from @viceice that Corepack adds a hash to the
packageManager
field inpackage.json
:Since
[email protected]
(PRs nodejs/corepack#413 and nodejs/corepack#291), this is performed:pnpm
oryarn
command is run, when nopackageManager
field present inpackage.json
corepack use <package manager>@<version>
is run, also when there is apackageManager
field present inpackage.json
Proposal
During Renovate updates of a package in the
packageManager
field: if a hash is found in thepackageManager
version, upgrade that hash version as well, eg. usingcorepack use <package manager>@<version>
Alternatives Considered
Another new GitHub Actions workflow, similar to my other GitHub Actions workflows:
link:
protocolBeta Was this translation helpful? Give feedback.
All reactions