Repository navigation
Pin Go, golangci-lint and goreleaser in mise.toml - #64
Merged
Merged
Conversation
The Go version was written out in five places across the two workflows, golangci-lint's in another, and none of it was pinned for local work, so my machine and CI could quietly drift apart. mise.toml is now the one place these versions live. CI installs them with jdx/mise-action, the lint step runs the golangci-lint mise put on PATH, and the release job runs goreleaser directly instead of through its action. setup-go used to cache Go modules and builds as well, which mise-action doesn't, so the test jobs now cache those themselves.
DomBlack
force-pushed
the
dom/mise-tools
branch
from
October 30, 2026 13:30
446f0af to
d646c7d
Compare
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 Go version was written out in five places across the two workflows and golangci-lint's in another, and nothing was pinned for working locally, so my machine and CI could quietly drift apart.
So mise.toml is now the one place those versions live, and CI installs them with jdx/mise-action. The lint step runs the golangci-lint mise put on PATH (install-mode none) rather than downloading its own, and the release job just runs goreleaser rather than going through goreleaser-action.
The release workflow only runs on a tag, so this PR doesn't exercise it. It's the same mise setup as the CI jobs though, plus goreleaser 2.x, which is what the action was resolving anyway.
setup-go was also caching Go modules and the build cache, which mise-action doesn't (it only caches the toolchain), so the Go jobs now cache those themselves with actions/cache, keyed on go.sum and mise.toml.