fix(ci): install Go 1.25 before monorel for release-pr / release#77
Merged
Conversation
monorel v0.12+ runs `go mod tidy` per sub-module as part of `pr` and
`release` to refresh go.sum entries. Every sub-module's go.mod
requires `go 1.25.0`, but the GitHub runner default is older and the
monorel CI action sets GOTOOLCHAIN=local, so the toolchain doesn't
auto-upgrade. The tidy step then fails with:
go: go.mod requires go >= 1.25.0 (running go 1.24.13;
GOTOOLCHAIN=local)
This bit the release-pr workflow when it ran on PR #76's merge commit
because monorel's `latest` tag had moved past v0.11.0 between PR #74's
release (v0.10.x) and PR #76's release (v0.13.0). The action version is
pinned (`@v0.11.0`), but the action invokes the binary under `latest`.
Add an `actions/setup-go@v5` step with `go-version: '1.25'` before the
monorel invocation in both release-pr.yml and release.yml. Mirrors the
setup-go pattern that ci.yml already uses for the regular CI matrix.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 3, 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
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.
Summary
The
release-prworkflow fails on push-to-mainafter a sub-module touched by a changeset requires Go 1.25 (every sub-module does). Run 25272224403 is the surfaced incident.Root cause
monorelv0.12+ runsgo mod tidyper sub-module as part ofprandreleaseto refresh go.sum entries. The GitHub runner default Go is older than 1.25 and the monorel CI action setsGOTOOLCHAIN=local, so the toolchain doesn't auto-upgrade. Tidy then fails on every sub-module.The action version is pinned (
disaresta-org/monorel/ci/github@v0.11.0), but the action invokes the monorel binary underlatest. Between PR #74's release-pr run (which resolvedlatestto ≤v0.11.0) and PR #76's run, monorel published v0.12.0 and v0.13.0. PR #76's run picked up v0.13.0, which surfaces the toolchain mismatch.Fix
Add
actions/setup-go@v5withgo-version: '1.25'before the monorel invocation in bothrelease-pr.ymlandrelease.yml. Mirrors the setup-go pattern thatci.ymlalready uses for the regular CI matrix.This is robust against future monorel version bumps that need newer toolchains, since the runner now always has 1.25 (and Go's default
GOTOOLCHAIN=autowould auto-upgrade past 1.25 if a sub-module ever requires it; the monorel action'sGOTOOLCHAIN=localonly blocks the auto-download, not a pre-installed newer version).Test plan
release-prand the workflow completes successfully (release PR opens / updates).releaseworkflow runs the publish pipeline cleanly.🤖 Generated with Claude Code