Repository navigation
Yarn v4 lock file maintenance fails in monorepo with Yarn v1 #46381
Unanswered
MikeMcC399
asked this question in
Request Help
Replies: 2 comments
|
Original issue where this occurred in a production repo is cypress-io/github-action#1910 |
0 replies
|
Is there any chance of getting a review on this issue sometime soon? I've had to disable Yarn 4 maintenance to work around this in https://github.com/cypress-io/github-action/blob/master/renovate.json I realize it may be an edge case to have mixed package managers in one monorepo. The reason is that these are in different example directories which show how to the use the GitHub JavaScript action https://github.com/cypress-io/github-action with some commonly used package managers (npm, pnpm, Yarn v1 Classic & Yarn v4 Modern). |
0 replies
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.
How are you running Renovate?
A Mend.io-hosted app
Which platform you running Renovate on?
GitHub.com
Which version of Renovate are you using?
44.103.0
Please tell us more about your question or problem
Minimal reproduction with README on https://github.com/MikeMcC399/renovate-yarn-mixed
Failed PR on MikeMcC399/renovate-yarn-mixed#5
When a GitHub monorepo contains a mixture of Yarn v1 and Yarn v4 projects, the lock file maintenance for Yarn v4 may fail with
Artifact update problem
It appears that Corepack is not being correctly installed / enabled. Corepack documentation advises to uninstall globally installed Yarn before installing Corepack (
npm uninstall -g yarn pnpm).Logs (if relevant)
Full log details and analysis on https://github.com/MikeMcC399/renovate-yarn-mixed#readme
Error portion example is:
Logs
All reactions