Repository navigation
Lint with golangci-lint v2.15.0, which reads Go 1.27.2's export data - #4
Merged
Merged
Conversation
The lint job sets up stable Go, now 1.27.2, and golangci-lint v2.13.2 fails its typecheck there: "export data version 5 is greater than maximum supported version 4". v2.15.0 reads it, and fetch, eventbus, leakcheck, seqdiff and lazyjson each lint to 0 issues on it, as on v2.13.2 with go1.27.1. Same bump as headlesslab/wand#148, which keeps the two equal. Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Oct 18, 2026
Fly-Playgroud
added a commit
to headlesslab/fetch
that referenced
this pull request
Oct 18, 2026
headlesslab/.github#4 moves the lint job to golangci-lint v2.15.0. v2.13.2 fails its typecheck on Go 1.27.2, the stable Go the job sets up, with "export data version 5 is greater than maximum supported version 4"; this module lints to 0 issues on v2.15.0.
Fly-Playgroud
added a commit
to headlesslab/eventbus
that referenced
this pull request
Oct 18, 2026
headlesslab/.github#4 moves the lint job to golangci-lint v2.15.0. v2.13.2 fails its typecheck on Go 1.27.2, the stable Go the job sets up, with "export data version 5 is greater than maximum supported version 4"; this module lints to 0 issues on v2.15.0.
Fly-Playgroud
added a commit
to headlesslab/seqdiff
that referenced
this pull request
Oct 18, 2026
headlesslab/.github#4 moves the lint job to golangci-lint v2.15.0. v2.13.2 fails its typecheck on Go 1.27.2, the stable Go the job sets up, with "export data version 5 is greater than maximum supported version 4"; this module lints to 0 issues on v2.15.0.
Fly-Playgroud
added a commit
to headlesslab/lazyjson
that referenced
this pull request
Oct 18, 2026
headlesslab/.github#4 moves the lint job to golangci-lint v2.15.0. v2.13.2 fails its typecheck on Go 1.27.2, the stable Go the job sets up, with "export data version 5 is greater than maximum supported version 4"; this module lints to 0 issues on v2.15.0.
Fly-Playgroud
added a commit
to headlesslab/leakcheck
that referenced
this pull request
Oct 18, 2026
headlesslab/.github#4 moves the lint job to golangci-lint v2.15.0. v2.13.2 fails its typecheck on Go 1.27.2, the stable Go the job sets up, with "export data version 5 is greater than maximum supported version 4"; this module lints to 0 issues on v2.15.0.
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.
The reusable
go.ymllint job sets upgo-version: stable, which is now Go 1.27.2, and golangci-lint v2.13.2 cannot read that toolchain's export data, so every satellite's next lint run fails its typecheck:It is what has been redding every pull request on wand since 2026-10-11; headlesslab/wand#148 makes the same bump there, and the comment beside wand's pin says the two stay equal.
Proof
Reproduced on fetch with v2.13.2 and go1.27.2 (the error above). Then each satellite, cloned at its
mainwith LF line endings and linted with its own.golangci.yml, or this repo's default for fetch, which has none:The satellites call this workflow at a pinned SHA, so each one picks the fix up when it moves its pin to the merge commit.