Repository navigation
Let renovate keep the dependencies current on its own - #73
Merged
Merged
Conversation
This was referenced Sep 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Renovate runs on this repo and Dependabot did too, and both write
go.modandgo.sum. Renovate merges a mockzilla bump the day it is tagged, which leavesevery open Dependabot branch conflicting until Dependabot merges main back into
it, and then the next bump lands and it conflicts again. PRs #47 and #61 have
been going round that loop for weeks.
Renovate already covers what the config here asked for, in one grouped pull
request a week, and both bumps those two PRs carry are queued in it.
Anyone making a repo from this template gets no dependency updates now. That is
a README line rather than a config we cannot switch off on our own copy.