Skip to content

chore(ci): bump Go toolchain to 1.26 - #108

Merged
brentrager merged 2 commits into
mainfrom
chore/go-1.26
Aug 25, 2026
Merged

chore(ci): bump Go toolchain to 1.26#108
brentrager merged 2 commits into
mainfrom
chore/go-1.26

Conversation

@brentrager

@brentrager brentrager commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

1. Bump the Go toolchain to 1.26

Since the mise migration the version lives only in mise.toml, so this is a one-line change.

Deliberately not touching the go directive in any go.mod (or go/go.work) — that declares the minimum language version for consumers of the published modules, and raising it would break them.

Verified locally on go1.26.7, every module CI loops over (for m in . fiber gin), with -count=1 to match CI:

module go build ./... go vet ./... go test -count=1 ./... gofmt -l .
go/ OK OK ok github.com/SmooAI/observability/go 3.464s clean
go/fiber OK OK ok github.com/SmooAI/observability/go/fiber 0.283s clean
go/gin OK OK ok github.com/SmooAI/observability/go/gin 0.385s clean

scripts/check-go-modules.sh also passes (exit 0): no replace directives, module paths match directories, /vN suffix matches major 0.

No Go 1.26 incompatibilities found.

2. Fix the paths-filter that made commit 1 a false green

The first commit's CI run reported success having compiled nothing. The changes gate filters on per-language directories, and mise.toml was in none of them — so go, rust, python, dotnet, desktop and ts all skipped. A toolchain bump is the one change that affects every lane and the one change that triggered none of them.

Second commit adds mise.toml to all six filters. Costs nothing on normal PRs (rarely touched), and makes a toolchain PR actually exercise the toolchain.

publish.yml is unaffected — it has no path filters and always runs the full matrix.

🤖 Generated with Claude Code

https://claude.ai/code/session_013YaefW6U442PHZf94fMAer

The toolchain version lives only in mise.toml since the mise migration,
so this is a one-line change. Deliberately NOT touching the `go`
directive in go.mod — that declares the minimum language version for
consumers of the published module, and raising it would break them.

Verified: go build/vet/test and gofmt all pass on 1.26.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@changeset-bot

changeset-bot Bot commented Aug 25, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 3d8467d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

…something

The Go 1.26 PR on this branch went green having compiled nothing: the
change-gate filters list only per-language directories, and mise.toml is
in none of them, so every lane skipped. A toolchain bump is the one change
that affects all six lanes and the one change that triggered zero of them
— the exact false green the gate exists to prevent.

Adding mise.toml to each filter costs nothing on normal PRs (it is rarely
touched) and makes a toolchain PR actually exercise the toolchain.

publish.yml is unaffected — it has no path filters and always runs the
full matrix.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@brentrager
brentrager merged commit f919b28 into main Aug 25, 2026
8 checks passed
@brentrager
brentrager deleted the chore/go-1.26 branch August 25, 2026 00:45
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