Announcing upgrade to Go 1.27 #72051
dillon-zheng
started this conversation in
General
Replies: 1 comment
|
Update (2026-10-22): darwin packages now require macOS 13+, ahead of the toolchain upgrade Heads-up for consumers of our darwin packages: the macOS build machines have been upgraded to macOS 13.7.8 in preparation for Go 1.27, and this already changes what we publish
This is the same floor that Go 1.27.2 will require anyway — it just takes effect earlier. The Go 1.27.2 upgrade itself is still in progress. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Dear developers,
We're planning to upgrade the Go version used in several core PingCAP repositories from Go 1.25.14 → Go 1.27.2.
Go 1.25 reached end of support when Go 1.27 was released (August 2026), and 1.25.14 was its final patch release. This upgrade keeps our builds on a supported toolchain and picks up the improvements introduced in Go 1.26 and Go 1.27:
encoding/jsonis now backed by the newencoding/json/v2implementationRelease notes: Go 1.26 · Go 1.27
Repositories affected
We will also align the related repositories that must be built with the exact same toolchain — such as tikv/client-go — so that downstream binaries stay compatible.
What will change
Notes for downstream users
Go maintains its compatibility promise, so we do not expect source-level breaking changes for typical users. A few behavior changes are still worth calling out if you build or ship these components yourself:
encoding/jsonis now backed by the newencoding/json/v2implementation. Behavior is preserved, but error messages may differ and the new implementation applies stricter rules by default.asynctimerchanbehavior has been removed, so timer channels are always unbuffered (synchronous).encoding/json/v2,encoding/json/jsontext,uuid, andcrypto/mldsaare now available.Timeline
How we validate before merging
Feedback and discussion
We welcome community feedback before we proceed with the upgrade.
Please share any concerns, compatibility notes, or suggestions in this discussion thread — especially if:
Thank you for your continued support and contributions!
— The PingCAP Engineering Team
All reactions