Repository navigation
ci: lint the Go 1.27 job on go1.27.1 until golangci-lint reads 1.27.2 export data - #119
Merged
Merged
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.
What
CI on master fails every night in the
1.27.xgolangci-lint step, withtypecheckerrors likeexport data version 5 is greater than maximum supported version 4.setup-gonow resolves1.27.xto Go 1.27.2. That release writes export data version 5, and golangci-lint's bundledgolang.org/x/toolsreads only up to version 4. The other jobs show as failed only because fail-fast cancels them.This sets
GOTOOLCHAIN=go1.27.1on the golangci-lint step, for the1.27.xjob only. Build, govulncheck and tests still run on the latest 1.27, and the1.26.xjob is unchanged.Testing
Locally, with go1.27.2 as the installed Go:
GOTOOLCHAIN=go1.27.1