Decouple CI Go version from go.mod#674
Merged
Merged
Conversation
Switch all CI workflows from go-version-file: 'go.mod' to go-version: 'stable' so CI always uses the latest stable Go release. This eliminates mechanical patch-bump PRs and ensures shipped artifacts (binaries, images) include all Go security patches automatically. The go.mod go directive continues to declare the minimum Go version required by the module, which is what matters for the enterprise go.work workspace and downstream consumers. This also fixes the failing govulncheck CI — the stdlib vulnerabilities (GO-2026-4946, 4947, 4870, 4869, 4866, 4865) are fixed in Go 1.26.2 which 'stable' will pick up. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add GO-2026-4771 (CVE-2026-33815) and GO-2026-4772 (CVE-2026-33816) to the govulncheck exclusion list. Both affect pgproto3 server-side message decoding (Bind.Decode, FunctionCall.Decode) and have no fixed version yet. This project is a PostgreSQL client connecting to trusted database servers, so the attack surface is minimal. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
ChrisJBurns
approved these changes
Apr 8, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #674 +/- ##
==========================================
+ Coverage 60.49% 60.51% +0.02%
==========================================
Files 101 101
Lines 9593 9593
==========================================
+ Hits 5803 5805 +2
+ Misses 3291 3290 -1
+ Partials 499 498 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
3 participants
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.
Summary
go-version-file: 'go.mod'togo-version: 'stable'so CI always uses the latest stable Go releasestablepicks up automaticallyContext
We've been pinning Go to the patch version in
go.mod(e.g.,go 1.26.1), which couples the CI Go version togo.modand requires a PR for every Go patch release. This decouples them:go.moddeclares the minimum Go version the module needs (unchanged for now — blocked on upstream dependencies liketoolhivewhich also patch-pin)go.moddeclaresgo.workcontinues to control the exact Go version for the workspace buildSimilar approach to theupdateframework/go-tuf#726.
Follow-up (blocked on upstream)
Once
toolhiveand other leaf dependencies drop their patch pins, we can also updatego.modto usego 1.26(minor only) +toolchain go1.26.1. Currentlygo mod tidyreverts this becausetoolhive@v0.15.0requiresgo 1.26.1.Test plan
go-version: 'stable'govulncheckworkflow usesgo-version-input: 'stable'correctly🤖 Generated with Claude Code