Skip to content

chore: lower go.mod directive from 1.26 to 1.25 (closes #70)#71

Merged
xe-nvdk merged 1 commit intov6from
fix/go-mod-1.25
Apr 27, 2026
Merged

chore: lower go.mod directive from 1.26 to 1.25 (closes #70)#71
xe-nvdk merged 1 commit intov6from
fix/go-mod-1.25

Conversation

@xe-nvdk
Copy link
Copy Markdown
Member

@xe-nvdk xe-nvdk commented Apr 27, 2026

Summary

  • Lowers the go.mod directive from 1.26 to 1.25 to restore drop-in compatibility for downstream consumers still on Go 1.25 (reported in is it possible to use Go 1.25? #70).
  • The original bump to 1.26 in 8cb2d99 was a modernization decision, not a code requirement. The codebase only relies on 1.21+ builtins (min, max, clear); no 1.22+ language features (range-over-int, iterators) or 1.26-only stdlib APIs are in use.
  • CI matrix in .github/workflows/build.yml already covers 1.25.x and 1.26.x, so 1.25 support is continuously exercised — no workflow change needed.
  • CHANGELOG entry added under v6.1 (unreleased) > Chores. The historical v6.0.0 note about the original 1.26 bump is intentionally preserved as accurate history.

Closes #70.

Test plan

  • go vet ./... — clean
  • go build ./... — clean
  • go test ./... — pass
  • go test -race ./... — pass
  • CI green on both Go 1.25.x and Go 1.26.x

🤖 Generated with Claude Code

Preserves drop-in compatibility for downstream users still on Go 1.25,
addressing the migration friction reported in #70 (forced toolchain bump
when moving from vmihailenco/msgpack/v5 to this fork).

The original bump to 1.26 was a modernization decision, not a code
requirement. The codebase only depends on 1.21+ builtins (min, max,
clear); no 1.22+ language features or 1.26-only stdlib APIs are in use.
CI matrix already covers 1.25.x and 1.26.x, so no workflow changes are
needed and 1.25 support is exercised on every PR.

Verified locally: go vet, go build, go test, and go test -race all pass
under the new directive.

Closes #70
@xe-nvdk xe-nvdk merged commit 034dc4b into v6 Apr 27, 2026
3 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.

is it possible to use Go 1.25?

1 participant