When updating groups where at least one package is lockfile-only, re-runs lose all package.json updates #32851
Replies: 3 comments 7 replies
-
|
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. Please follow these steps:
If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide. The Renovate team |
Beta Was this translation helpful? Give feedback.
-
|
Please see our automated guide to reproductions. Your repo is missing a description, also has some unnecessary complexity |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, We're closing this discussion because it's missing some details, or because something else about it made it hard or impossible for us to help resolve the issue. We want high quality discussions, so users can search them for answers. This means we'll close (and later delete) low quality discussions. You are welcome to create a new discussion with more details in future. Thanks, the Renovate team. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitHub
Please tell us more about your question or problem
If you have a group of packages configured, and at least one package in the group needs a package.json update while at least one other package in the group needs a lockfile-only update, Renovate re-runs will frequently lose all package.json updates from the PR.
More specifically: On the first run it creates the PR for the group normally. On the second run it finds no package.json updates are needed (because the PR already contains them) but still sees that there's a package with a lockfile-only update, so it redoes the PR with only the lockfile update (throwing away the package.json changes). A third re-run will redo the package.json updates.
Minimal reproduction repo: https://github.com/anomiex/renovate-test/
Logs (if relevant)
Logs
https://github.com/anomiex/renovate-test/actions/runs/12126600506
Beta Was this translation helpful? Give feedback.
All reactions