Skip to content

chore(deps): update dependency go to v1.27.2 - #808

Merged
tannevaled merged 1 commit into
mainfrom
renovate/go-1.x
Oct 9, 2026
Merged

tannevaled merged 1 commit into
mainfrom
renovate/go-1.x

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
go uses-with patch 1.27.1 → 1.27.2

Release Notes

actions/go-versions (go)

v1.27.2: 1.27.2

Compare Source

Go 1.27.2


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@tannevaled
tannevaled merged commit 3aed678 into main Oct 9, 2026
9 checks passed
@tannevaled
tannevaled deleted the renovate/go-1.x branch October 9, 2026 19:17
tannevaled added a commit that referenced this pull request Oct 9, 2026
…ocks this branch

Two things were each other's blocker, and merging the other one fixes the first.

THE RED LANES. This branch raised the go directive to 1.27.2 while the CI
workflows were still pinned to 1.27.1, so every lane said:

    go: go.mod requires go >= 1.27.2 (running go 1.27.1; GOTOOLCHAIN=local)

That is GOTOOLCHAIN=local doing its job: refusing to silently fetch a newer
toolchain and measure something other than what the pin names. #808 raises the
pins to 1.27.2 and is merged, so merging main into this branch clears it.

THE README. Renovate moved go.mod and left all three statements of the minimum
behind. The guard named every one of them rather than just the badge:

    README Go badge claims 1.27.1, go.mod requires 1.27.2
    README states a Go minimum of 1.27.1 in "badge/go-1.27.1%2B"
    README states a Go minimum of 1.27.1 in "Go 1.27.1+"

which is what #793/#795 added it for -- the badge alone had been fixed twice
while the prose went on being wrong.

Worth recording for whoever measures next: on this machine the go binary under
.../v1.27.1/bin reports go1.27.2, because GOTOOLCHAIN=auto downloaded and ran
1.27.2 the moment the directive asked for it. The PATH names a version; it does
not run one. GOTOOLCHAIN=local is the only way to find out, and it is why CI
sets it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
tannevaled added a commit that referenced this pull request Oct 10, 2026
Renovate force-pushed this branch over 12f5759 -- a commit that had corrected
both statements of the Go minimum and gone GREEN on ci and rubyspec-ratchet --
reinstating 1.27.1 against the 1.27.2 directive the same branch sets. So the
badge guard fails again, on exactly the lines it failed on before.

Re-applied. The durable half is #810, which replaces the badge with one that
READS go.mod (shields.io's github/go-mod/go-version) so there is one
hand-written copy left instead of two; that one still has to be corrected by
hand, and the guard still names it every time.

Worth knowing for whoever reads these lanes next: the five red checks on this
branch were never about these dependency bumps. They were
`go: go.mod requires go >= 1.27.2 (running go 1.27.1; GOTOOLCHAIN=local)` --
every lane stopped at `go vet`, before a single dependency was exercised. The
other half of that pair was #808, now merged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
tannevaled added a commit that referenced this pull request Oct 11, 2026
The only red check left on this branch, and the LAST hand-written copy of the
number: #810 made the badge read go.mod, so there is one statement to correct
instead of two, and the guard named it exactly.

    readme_go_floor_test.go:83: README states a Go minimum of 1.27.1
      in "Go 1.27.1+"; go.mod requires 1.27.2

Everything else on this branch is green -- internal/vm passes in 373s on
arch amd64, and the dependency bumps themselves are being exercised for the
first time, since every earlier run on this branch stopped at `go vet` on the
toolchain pin (#808, merged).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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