Repository navigation
ci: move the Go pin from 1.27.1 to 1.27.2 - #115
Merged
Merged
Conversation
4 occurrence(s) in ci.yml. Pinning was right: an alias has no version to review. But a pinned fleet cannot move, and a Go patch release is usually a SECURITY release -- the standard library is compiled into every binary, so the toolchain that built it is the toolchain it carries. An EXACT move: -from 1.27.1 names the version to change, so a job held back on purpose at some other version is not a candidate and is left as it is. go.mod is not raised: the directive is a minimum for consumers, and the workflow pin is what builds the artefacts. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
This repository pins Go 1.27.1 in
ci.yml— 4 occurrence(s). This moves them to 1.27.2.Why move a pin that is already explicit
Pinning was the right thing: an alias has no version to review. But a pinned fleet cannot move, and a Go patch release is usually a security release — the standard library is compiled into every binary, so the toolchain that built it is the toolchain it carries.
Check what this one fixes with
govulncheck ./...against both versions, rather than taking the release notes' word for whether it reaches this code.It moves an exact version, and only that one
-from 1.27.1names the version to move. "Anything older" cannot tell a stale pin from a deliberate one, so a job held back on purpose at some other version is not a candidate here and is left exactly as it is.go.modis not raised. The directive is a minimum for consumers; the workflow pin is what builds the artefacts.🤖 Generated with Claude Code