Skip to content

ci(release): bump golangci-lint pin to v2.15.0 (Go 1.27) - #59

Merged
louisgls merged 1 commit into
mainfrom
ci/release-lint-pin
Oct 21, 2026
Merged

louisgls merged 1 commit into
mainfrom
ci/release-lint-pin

Conversation

@louisgls

Copy link
Copy Markdown
Collaborator

Why

#58 moved the module to Go 1.27 and bumped the golangci-lint pin in golangci-lint.yml, but release.yml carries its own pin and stayed at v2.11.4. That binary is built with go1.26 and refuses to run:

can't load config: the Go language version (go1.26) used to build golangci-lint is lower than the targeted Go version (1.27.3)

Result: the lint gate failed on the v1.9.2 Release run, so build/release were skipped and v1.9.2 has no signed binaries / GitHub Release. The Docker image 1.9.2 and chart 1.10.2 published fine (separate workflows).

Change

release.yml: golangci-lint v2.11.4 → v2.15.0 (go1.27 support since v2.13.0), same as golangci-lint.yml.

After merge

The Release workflow only runs from a v* tag ref, so publishing binaries needs either a v1.9.3 cut or moving v1.9.2 — to decide.

🤖 Generated with Claude Code

The Release workflow pins golangci-lint separately from the Go lint
workflow and was left at v2.11.4 when the module moved to Go 1.27. That
binary is built with go1.26 and refuses to load the config ("Go language
version used to build golangci-lint is lower than the targeted Go
version"), so the lint gate failed on v1.9.2 and the signed binaries were
not published.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@louisgls
louisgls merged commit bfbf5d9 into main Oct 21, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant