Upgrade Go 1.25 → 1.26#11
Open
asparuhft wants to merge 1 commit into
Open
Conversation
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
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.
Description
What
Automated upgrade of Go references from
1.25to1.26.go.mod: bumped only when it declaredgo 1.25golang:1.26(preserving tag suffixes like-alpine)go-version, andGO_VERSIONvars updated (1.26).go-version/.tool-versions: set to1.26A
go mod tidywas run for modules that changed.Why
Estate-wide alignment on Go
1.26to match current platform/tooling and reduce drift.Link to ticket: https://financialtimes.atlassian.net/browse/UPPSF-7052
Anything, in particular, you'd like to highlight to reviewers
Scope and particulars of this PR (Please tick all that apply)
DoD - Ensure all relevant tasks are completed before marking this PR as "Ready for review"
This Pull Request follows the rules described in our Pull Requests Guide