Lock file PR not getting updated if already open (unless "rebase" checkbox ticked) #9190
-
What Renovate type, platform and version are you using? Self-hosted Describe the bug When a "lock file maintenance" PR is already it open, it does not get updated even if there are new items to be updated in there. If the PR has This has regressed quite a while ago (several months?), I just didn't have time to raise the bug until now... Relevant debug logs
When the "rebase" checkbox is ticked, the following line is also present:
Have you created a minimal reproduction repository? Please read the minimal reproductions documentation to learn how to make a good minimal reproduction repository.
Additional context Creating a repro case is a bit involved, but I can possibly do it if this does not have enough information. We have the following in the config:
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 8 replies
-
Renovate only See rebaseWhen |
Beta Was this translation helpful? Give feedback.
-
This is not about rebasing - it does not need to rebase - it needs to update the lock file, but it does not update the lock file, unless the "rebase" option is ticked. It does update e.g. the |
Beta Was this translation helpful? Give feedback.
-
Renovate doesn't perform lock file maintenance non-stop as it would be too inefficient. To know if it needs updating, it would have to do a full install every single run, which is not a good idea. The current behavior is therefore by design. |
Beta Was this translation helpful? Give feedback.
-
That's fine - that's by configuration - it makes perfect sense to not do it on every run. However if the PR is open, it does not perform it at all (even if the scheduled date has been hit, or if you set up to perform it every time. I would expect the PR to get updated (on schedule)? |
Beta Was this translation helpful? Give feedback.
Renovate doesn't perform lock file maintenance non-stop as it would be too inefficient. To know if it needs updating, it would have to do a full install every single run, which is not a good idea. The current behavior is therefore by design.