chore: run go1.26.3 fix ./...#3970
Merged
Merged
Conversation
moskyb
approved these changes
Jun 9, 2026
Contributor
|
Should we update the agent to use 1.26 as its default toolchain? |
Contributor
Author
Yeah maybe! |
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.
Description
Automatically update some anachronistic Go using
go fixfrom Go 1.26.Context
Some
interface{}has snuck in, reported in #3967 but that PR deleted a bunch of code instead of fixing it.Changes
As generated by
go1.26.3 fix ./....Testing
go test ./...). Buildkite employees may check this if the pipeline has run automatically.go tool gofumpt -extra -w .)Disclosures / Credits
The Go team for creating
go fix.