Best Practice for arbitrarily ignoring certain updates? #8953
-
What is the best practice for ignoring MRs for packages you DO NOT want to upgrade (usually Here is an example of what I mean...
So, currently, I'm just manually upgrading dependencies, so I just keep a log of which dependencies I do not want to update for one reason or another. Since (I assume) Renovate is going to create an MR for The docs are expansive, so I wasn't sure if there was an elegant way to "manage" this in Renovate (beyond just using I guess I'm looking for an "ignore until something else happens" functionality... like a way to configure Renovate to "only open MRs for dependencies that have compatible sub-dependencies in the same If I just use |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Use dependency dashboard approval. So you see all updates in one issue and can approve when you are ready. Approval requirement can be assigned via package rules. |
Beta Was this translation helpful? Give feedback.
Use dependency dashboard approval.
So you see all updates in one issue and can approve when you are ready.
Approval requirement can be assigned via package rules.