Stop pinning Go to patch versions, use stable in CI#1137
Merged
Conversation
d318442 to
2e1ea2e
Compare
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
2e1ea2e to
0a9b73f
Compare
tadasant
approved these changes
Apr 9, 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
2 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.
Motivation and Context
We keep bumping
go 1.26.xacross the repo every time a new Go patch dropsHow Has This Been Tested?
go.mod/deploy/go.mod:go 1.25.8→go 1.26(minor only — "this module needs Go 1.26")go-version-file: 'go.mod'→go-version: 'stable'— CI always uses the latest stable Go, no morebump PRs
go-version-input: '1.26.1'→go-version-input: 'stable'Breaking Changes
Types of changes
Checklist
Additional context