feat: track the go.mod go directive in Renovate#52
Merged
Conversation
Renovate's built-in gomod manager deliberately does not bump the bare go.mod `go` directive (it treats `go 1.26.4` as a >= minimum-version constraint), so a Go stdlib CVE fix never reaches go.mod and the go-ci govulncheck step keeps failing until a manual bump. Observed 2026-07: go.mod was stuck at 1.26.4 fleet-wide (GO-2026-5856, the crypto/tls ECH leak, fixed in go1.26.5) while the Dockerfile ARG GO_VERSION had already advanced via the existing customManager. Add a customManager that tracks the `go X.Y.Z` directive via the golang-version datasource, grouped with the existing "golang toolchain" rule so it lands in one PR with any Dockerfile GO_VERSION bump. Minor/patch auto-merge, majors gated.
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.
feat: track the go.mod go directive in Renovate
Renovate's built-in gomod manager deliberately does not bump the bare go.mod
godirective (it treatsgo 1.26.4as a >= minimum-version constraint), soa Go stdlib CVE fix never reaches go.mod and the go-ci govulncheck step keeps
failing until a manual bump. Observed 2026-07: go.mod was stuck at 1.26.4
fleet-wide (GO-2026-5856, the crypto/tls ECH leak, fixed in go1.26.5) while the
Dockerfile ARG GO_VERSION had already advanced via the existing customManager.
Add a customManager that tracks the
go X.Y.Zdirective via the golang-versiondatasource, grouped with the existing "golang toolchain" rule so it lands in
one PR with any Dockerfile GO_VERSION bump. Minor/patch auto-merge, majors gated.