Skip to content

chore: upgrade to Go 1.27 + go fix modernize - #138

Merged
lehainam-dev merged 2 commits into
main-kafkafrom
chore/go-1.27
Oct 22, 2026
Merged

lehainam-dev merged 2 commits into
main-kafkafrom
chore/go-1.27

Conversation

@lehainam-dev

@lehainam-dev lehainam-dev commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Bump Go 1.22 → 1.27 in go.mod, the Dockerfile, and the CI/release workflows.
  • Apply go fix ./... modernizers: interface{} → any, strings.Builder in FormatKey, slices.Backward in RedisBlockKeeper.Init, and the Redis config built in a single struct literal.
  • Bump golangci-lint v1.59.1 → v2.14.0 and golangci-lint-action v3 → v9. v1.59.1 was built with Go 1.22 and refuses to lint a go 1.27 module; Go 1.27 support starts at v2.13.0. Dropped skip-pkg-cache / skip-build-cache, which the action no longer accepts.
  • Exclude staticcheck QF1008: explicit embedded-field selectors such as k.BaseBlockKeeper.Add() are intentional in wrapper types.

Testing

  • go build, go vet and go test -race ./... pass on Go 1.27.0.
  • golangci-lint v2.14.0 with the repo config: 0 issues.

Deploy note

Raising the go directive from 1.22 to 1.27 also changes GODEBUG defaults. For example, post-quantum TLS key exchange is on by default since Go 1.24. There is no explicit TLS config in this repo, but watch wss:// and https RPC connections after deploy.

🤖 Generated with Claude Code

- Run `go fix ./...` (interface{} -> any, strings.Builder, slices.Backward,
  struct literal fields).
- Bump golangci-lint to v2.14.0 (first Go 1.27 support is v2.13.0) and
  golangci-lint-action to v9; drop inputs removed from the action.
- Exclude staticcheck QF1008: explicit embedded-field selectors are
  intentional in wrapper types.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@lehainam-dev
lehainam-dev merged commit 035ef18 into main-kafka Oct 22, 2026
4 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