is it possible to use Go 1.25?

[hajimehoshi]

Issue tracker is used for reporting bugs and discussing new features. Please use
Discord or stackoverflow for supporting
issues.

Expected Behavior

I'm trying to migrate from github.com/vmihailenco/msgpack/v5 to github.com/Basekick-Labs/msgpack/v6, but this required to update the Go version to 1.26 unexpectedly. This can be a little risky at least to us. Would it be possible to stick to 1.25? Thanks,

Current Behavior

go.mod specifies Go 1.26 and all the dependencies on this library would need to update the Go version.

Possible Solution

Modify go.mod to use Go 1.25 or 1.25.0

Steps to Reproduce

Context (Environment)

Detailed Description

Possible Implementation

[xe-nvdk]

Hi @hajimehoshi — thanks for the report, and apologies for the unexpected toolchain bump.

You're right: the jump to go 1.26 in 8cb2d99 was a modernization decision, not a code requirement. We don't use any 1.26-only language features or stdlib APIs — the only modern builtins in the codebase are min/max/clear, which all land in Go 1.21. CI already runs the matrix against 1.25.x and 1.26.x, so 1.25 support is continuously exercised.

I've opened #71 to lower the go.mod directive back to 1.25. Verified locally with go vet, go build, go test, and go test -race — all green.

Once #71 merges to v6, we'll cut a v6.1.0 release so the fix is available via go get github.com/Basekick-Labs/msgpack/v6@latest without you having to pin a commit. (The go 1.26 directive is in the current v6.0.0 tag, so a new release is required for module-resolver consumers — the merge alone isn't enough.)

If you need it before then, you can temporarily pin to the branch tip after merge:

go get github.com/Basekick-Labs/msgpack/v6@v6

Will follow up here when v6.1.0 is tagged.

[xe-nvdk]

v6.1.0 is out: https://github.com/Basekick-Labs/msgpack/releases/tag/v6.1.0

The go.mod directive is now back at go 1.25, so:

go get github.com/Basekick-Labs/msgpack/v6@latest

…should resolve to v6.1.0 without forcing a toolchain bump. Thanks again for flagging this — closing the issue, but feel free to reopen if you hit anything unexpected during migration.

[hajimehoshi]

Thanks!