Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go.mod: Use 1.22.0 instead of 1.22 #4614

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rata
Copy link
Member

@rata rata commented Feb 5, 2025

Before go 1.21, using "go 1.20" meant 1.20.0 and all patch releases, excluding rc releases of 1.20. However, since go 1.21, it means truncating everything after the 21: 1.21, 1.21rc2, and 1.21.3 all are accepted. See more info here:

Let's keep doing the same we always did and add the .0 for that. Other projects, like containerd and kubernetes, are also using the .0 now.

Before go 1.21, using "go 1.20" meant 1.20.0 and all patch releases,
excluding rc releases of 1.20. However, since go 1.21, it means
truncating everything after the 21: 1.21, 1.21rc2, and 1.21.3 all
are accepted. See more info here:

	https://go.dev/doc/toolchain#version

Let's keep doing the same we always did and add the .0 for that. Other
projects, like containerd and kubernetes, are also using the .0 now.

Signed-off-by: Rodrigo Campos <[email protected]>
@kolyshkin
Copy link
Contributor

So, this basically tells the users of this module that go1.22rc is not good enough? Is this really so?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants