deps: update renovate configuration - #338
Merged
phisco merged 1 commit intoAug 6, 2026
Merged
Conversation
Signed-off-by: Erhan Cagirici <erhan@upbound.io>
erhancagirici
requested review from
negz,
phisco,
sergenyalcin,
turkenf and
ulucinar
as code owners
August 6, 2026 11:28
phisco
approved these changes
Aug 6, 2026
1 task
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
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.
Description of your changes
Extends the renovate configuration with custom managers and some noise tweaking
Static validation with
renovate-config-validator --strictand tested with the local mode.Global settings
prConcurrentLimit: 5— cap parallel Renovate PRs.baseBranchPatterns: ["main"]— only targetmain.labels: ["automated", "renovate"]— all PRs are labeled.vulnerabilityAlertsandosvVulnerabilityAlertsexplicitly, so the rules thatare deliberately disabled below still produce PRs for known CVEs.
fileMatchtomanagerFilePatternsandswitched to the regex-delimiter syntax, per the newer Renovate schema.
New custom regex managers
Bump versions that are embedded in CI files rather than a lockfile:
.github/workflows/*.yaml,DockerfileGO_VERSION,ARG GO_VERSION.github/workflows/*.yamlGOLANGCI_VERSION,GOLANGCILINT_VERSION.github/workflows/*.yamlDOCKER_BUILDX_VERSION.github/workflows/*.yamlXP_VERSION(assumes thestablechannel)New package rules
Kubernetes Go dependencies
k8s.io/client-goto<1.0, since old pre-semver tags are stillpublished in the repo.
patch/digestbumps ofk8s.io/**andsigs.k8s.io/**into asingle "kubernetes patches" PR.
major/minorbumps require dependency dashboard approval — these shouldtypically follow
crossplane-runtimefor maximum compatibility.k8s.io/utilsandk8s.io/kube-openapi; they have no version tags and are best managedtransitively by the other k8s dependencies.
Crossplane Go dependencies (
github.com/crossplane/**)major/minor/patch(separateMajorMinor,separateMinorPatch,separateMultipleMinor).patchbumps flow automatically.major/minor/digestbumps require dependency dashboard approval, sincethey may involve actual development work.
Other Go dependencies
majorandminor/patch/digest. Combined with thevulnerability alert settings above, these only get PRs when there is a known
vulnerability in the current version.
GitHub Actions
minor/patchgrouped into a single "all non-major github action" PR.majorbumps get dedicated PRs.minimumReleaseAge: 3 daysandpinDigests: true.Grouping for CI tooling
crossplane/crossplane+crossplane/cli→ one "crossplane versions in CI" PR.golangci/golangci-lint→ its own "golangci-lint versions in CI" PR.go.mod(rangeStrategy: bump) is grouped with the CI envvars into a single "golang versions" PR, with
separateMinorPatchenabled.I have:
Added or updated unit tests for my change.(configuration-only change)