Deprecate Go 1.20.x (EOL) #424
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@brayanhenao can we do this now? |
brayanhenao
force-pushed
the
deprecate-go-1-20-x
branch
from
cb0988d
to
01d7924
Compare
@sophiewigmore Yes! I just updated the PR state. |
brayanhenao
force-pushed
the
deprecate-go-1-20-x
branch
from
01d7924
to
df01d5c
Compare
brayanhenao
force-pushed
the
deprecate-go-1-20-x
branch
from
df01d5c
to
c6a7abf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With the release of Go 1.22.x link, it's time to consider deprecating Go 1.20.x. Based on past experiences of encountering issues with new Go versions in the initial weeks, we've established a practice of waiting for one month (the next release cadence) before deprecating the old version and adding the new one. Therefore, this PR should be postponed until/around March, 2024.