Upgrade Go to 1.25 - #97
Closed
janhartman wants to merge 1 commit into
Closed
janhartman wants to merge 1 commit into
janhartman wants to merge 1 commit into
Conversation
janhartman
deleted the
go-1-25-upgrade-3a184972-bc3a-4496-b610-fc1409358dbf
branch
September 14, 2026 11:41
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.
Raises this repository's declared Go version to 1.25.
go.moddeclaring a version below 1.25 now declaresgo 1.25.0(and itstoolchaindirective, where present, is pinned togo1.25.0)..go-version/.tool-versions, build scripts, and docs — are raised to match, so builds don't silently run on an older toolchain.Dependencies are untouched: no
go mod tidy, nogo.sumchanges.One thing worth a look if this module was previously below
go 1.22: raising the language version changesforloop variable scoping to per-iteration. That is usually a bug fix, but it can alter behaviour in code that deliberately captured the shared loop variable.Created by a Sourcegraph agentic batch change.