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.
I'd like to give Renovate a try instead of manually updating this repository's dependencies every month. A motivating factor here is that I was looking into pinning github action versions manually, but then realized that would add even more toil to the manual process.
A goal is to have this be as free of noise as possible by grouping the go dependency updates (which was how it was done manually). That should run weekly (or can be triggered manually) to create a PR that won't auto-merge. I also disabled Dockerfile updates since the two candidates there are:
I'm no Renovate expert, but went through the configuration to try to understand what's going on. Most of
.github/workflows/renovate.yml
is similar to other grafana repositories where the workflow is present, with the exception of the cron scheduling and not providing aconfigurationFile
to theSelf-hosted Renovate
step (it seemed unnecessary)..github/renovate.json
is similar to others as well with the exception of theextends
andpackageRules
sections.