chore: bump all modules to go 1.26.0 - #273
Merged
Merged
Conversation
Go 1.25 is out of support since 1.27 shipped. Unifies the go directive across every published module (previously 1.19 to 1.25.0) and drops the stale toolchain line in linters/isolint. Lint testdata fixtures untouched.
This reverts commit c890c75.
yanyi-wego
approved these changes
Oct 2, 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
2 participants
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.
What
Sets
go 1.26.0in all 37 published modulego.modfiles (they ranged from 1.19 to 1.25.0), plus the two lint testdata fixtures and drops the staletoolchain go1.24.2inlinters/isolint.go mod tidywas run per module. The onlygo.modchanges are the directive lines and that toolchain removal, and nogo.sumfiles changed.Why
Go 1.25 has been out of support since 1.27 shipped. Dependabot bumps such as #269 (validator) already raise the floor to 1.26 one module at a time, so this makes the change once, across every module. Agreed with yanyi in #payments-pull-requests.
Impact
Consumers only need Go 1.26 when they next bump a wego/pkg module. Their existing pins keep building as they are. No consumer repos are changed here.
Testing
Ran
go build ./... && go vet ./... && go test -count=1 ./...with go1.26.8 in every module, and all modules that contain packages passed.httpandisocontain no packages, sogo vetexits non-zero there with "no packages to vet". The lint testdata fixtures are bumped too, because theyreplacelocal wego/pkg modules: with their old directive,analysistestfails with "updates to go.mod needed".After merge
Tag a minor version on every module, so the new Go floor shows up in the version number.