Repository navigation
Missing package updates in npm workspace and rangeStrategy: "update-lockfile"
#40474
Unanswered
Kakadus
asked this question in
Request Help
Replies: 2 comments
|
same here |
0 replies
|
|
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.
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?
42.74.5
Please tell us more about your question or problem
We're using npm workspaces and configured
rangeStrategy: "update-lockfile". We found that some dependencies inside the non-root packages aren't updated at all (while others are). Those packages are not mentioned in the update PR, even though they are correctly detected by renovate.In the logs, their update field is empty and their
currentVersionis already set to the latest version. If I mention the dependency in the rootpackage.json, the package is updated and mentioned in the PR.You can find a short reproduction here: Kakadus/renovate-repro#4
vitest(root & workspace) is updated correctly, while@vitest/browser-playwright(workspace-only) is not updated. Note that I have setlegacy-peer-deps=truein.npmrcthere. This is only to make the error more visible, as otherwise, npm would have bumped@vitest/browser-playwrightitself, obscuring the error further.Logs (if relevant)
Logs
All reactions