Skip to content

docs: the README badge still named the Go floor before 1.27.1 - #8

Merged
tannevaled merged 1 commit into
mainfrom
readme-badge-1271
Oct 7, 2026
Merged

tannevaled merged 1 commit into
mainfrom
readme-badge-1271

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

go.mod says go 1.27.1; the badge said otherwise, so the first thing a reader sees contradicted the module.

Only the shields.io badge is touched. A README names a Go version for more than one reason, and the other two must not move:

shields.io/badge/go-… the module minimum — stale, fixed here
"Measured on an Apple M4 Max, Go 1.26.4" a dated measurement — rewriting it would falsify it
"uses Go 1.26's experimental simd/archsimd" when an API appeared — rewriting it would make it wrong

Sampled before this was automated: of four repositories with a drifting README, three had prose that must not move. Hence badge only.

🤖 Generated with Claude Code

go.mod says `go 1.27.1`; the badge said otherwise, so the first thing a
reader sees contradicted the module.

Only the shields.io badge is touched. A README names a Go version for more
than one reason, and the other two must not move: a dated measurement
("Measured on ..., Go 1.26.4") would become false, and a statement about when
an API appeared ("uses Go 1.26's experimental simd/archsimd") would become
wrong. Changed mechanically, badge only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@tannevaled
tannevaled merged commit 8e7f941 into main Oct 7, 2026
11 checks passed
@tannevaled
tannevaled deleted the readme-badge-1271 branch October 7, 2026 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant