Backport of [NET-4968] Upgrade Go to 1.21 into release/1.17.x #20182
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #20062 to be assessed for backporting due to the inclusion of the label backport/1.17.
🚨
The person who merged in the original PR is:
@zalimeni
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.
The below text is copied from the body of the original PR.
Description
Upgrade Go to 1.21.
This is needed in advance of the EOL of Go 1.20 ~Feb. 1. The ideal timing is before our next patch release scheduled for the end of January.
A follow-up change will introduce
toolchain
directives to pin to the latest version; the hope is to use a root-levelgo.work
to accomplish this, which requires some additional changes to support. See #20058 for more context.That PR should set this change up to cleanly backport and sync without intervention 🤞🏻
Testing & Reproduction steps
Tests continue to pass, and Go 1.21 can be observed as the output of
get-go-version
.PR Checklist
Overview of commits