What would you like to be added?
Go 1.27.0 was released last week, which means that 1.25 no longer receives updates. According to our Dependency management documentation, we want our stable branches to stay on the oldest supported minor version, and our main branch to stay on the latest.
Progress track:
Please review the previous issues and their corresponding pull requests, such as #22309 and #22057.
Why is this needed?
To keep the project on supported Go versions.
What would you like to be added?
Go 1.27.0 was released last week, which means that 1.25 no longer receives updates. According to our Dependency management documentation, we want our stable branches to stay on the oldest supported minor version, and our main branch to stay on the latest.
Progress track:
main: go v1.27.0 - [DO NOT MERGE] Bump go toolchain to 1.27rc3 #22302release-3.7: go v1.26.7 (no action needed, already at 1.26.7)release-3.6: go v1.26.7 - [release-3.6] Bump go 1.26.7 #22334release-3.5: go v1.26.7 - [release-3.5] Bump go 1.26.7 #22335CHANGELOGmain: go v1.26.7 - bump go 1.26.7 bbolt#1269release-1.5: v1.26.7 - [release-1.5] bump go 1.26.7 bbolt#1270release-1.4: v1.26.7 - [release-1.4] bump go 1.26.7 bbolt#1271release-1.3: v1.26.7 - [release-1.3] bump go 1.26.7 bbolt#1272main: go v1.26.7 - no action neededrelease-3.7: go v1.26.7 - no action neededrelease-3.6: go v1.26.7 - [release-3.6] bump go 1.26.7 raft#508etcd-io/gofailmaster: go v1.26.7 - bump go 1.26.7 gofail#162etcd-io/augermain: go v1.27.0 - bump go 1.27.0 auger#519etcd-io/etcd-operator: go v1.27.0 - bump go 1.27.0 etcd-operator#486etcd-io/protodocmaster: go v1.26.7 - bump go 1.26.7 protodoc#37Please review the previous issues and their corresponding pull requests, such as #22309 and #22057.
Why is this needed?
To keep the project on supported Go versions.