Repository navigation
build: raise the Go floor to 1.27.1 - #785
Merged
Merged
Conversation
Raise the Go floor to 1.27.1. - go.mod: go 1.26.6 -> 1.27.1 - arch-qemu-nightly.yml: go-version stable -> 1.27.1 - ci.yml: go-version stable -> 1.27.1 - release.yml: go-version stable -> 1.27.1 - rubyspec-ratchet.yml: go-version stable -> 1.27.1 - go build ./... (host) ok Part of the fleet move to Go 1.27.1. Known risk, accepted: go1.27.0 and go1.27.1 still miscompile one loong64 pattern (golang/go#81000, backport golang/go#81147 pending for 1.27.2). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tannevaled
added a commit
that referenced
this pull request
Oct 7, 2026
…ooking (#793) * docs: the Go badge went stale when the floor moved, and nothing was looking #785 raised go.mod from 1.26.4 to 1.27.1. The README badge kept claiming 1.26.4 -- which is the claim a reader checks before depending on the module, and the one that decides whether their toolchain will even build it. I flagged this on the PR that raised the floor, as a loose end that its file list did not cover. It merged without it, which is the ordinary way a cross-file claim rots: the change was correct, the reviewer was me, and the fact lived in a file nobody had reason to open. So the badge is corrected AND given a guard, in the spirit of TestReadmeConformanceCountMatchesTheBaseline: the test reads the `go` directive out of go.mod and requires the shields.io badge to match it. A version badge is exactly the kind of fact that rots silently, because it is read by people and by no test. The guard was proved to fail before it was trusted -- a verification step that cannot be made to fail has not been tested: README Go badge claims 1.26.4, go.mod requires 1.27.1 It also sweeps the README for any other `go-1.x.y` claim, so a second mention in prose cannot drift independently of the badge. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs: the floor is stated TWICE, and the first guard only knew about one The README states the Go minimum in two places: line 7 [] line 716 Requires **Go 1.26.4+**. Both were stale against `go 1.27.1`. The first revision of this branch fixed the badge and added a guard -- and the guard swept for `go-1.x.y`, the shape I had just corrected, so it was blind to the prose one. A peer session opened #795 for the same defect and also touched only the badge. Two independent passes, one line each, and the second statement would have survived both. That is the failure worth recording: a guard written from the instance in front of me rather than from the claim being made. It could only ever have caught what I had already found. So the guard now judges the CLAIM -- every statement of a minimum -- and not the markup it wears. It also requires at least two such statements to exist, so that deleting one silently stops being a way to pass. It deliberately does NOT fail on every mention of a Go version, which is the distinction #795's body draws and is right about: a dated measurement ("measured on Go 1.26.4") would be FALSIFIED by updating it, and "Go 1.26 introduced X" is a fact about when an API appeared. Neither tracks go.mod. Only the two forms that state a minimum are matched. Those other two kinds do not currently appear in this README -- `grep` finds exactly the two lines above -- but the guard is written so that adding one later does not turn it red. Proved to fail on the prose form, not only the badge: README states a Go minimum of 1.26.4 in "Go 1.26.4+"; go.mod requires 1.27.1 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- 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.
Raise the Go floor to 1.27.1.
Part of the fleet move to Go 1.27.1. Known risk, accepted: go1.27.0 and go1.27.1 still miscompile one loong64 pattern (golang/go#81000, backport golang/go#81147 pending for 1.27.2).
🤖 Generated with Claude Code