-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Can't run against "rc" versions of Go #4318
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
Comments
related to #4273 |
I think a bug with |
I will improve our |
Thanks! Is there a schedule for tagged releases? |
My current plan is to wait for the release of go1.22, based on the previous Go release, this should happen in a few weeks (beginning of February). |
Any way I can beg for a tag before? This bug is (partially) preventing
kubernetes from adopting the Go release-candidate in master, so we can get
some soak time before release.
…On Sun, Jan 14, 2024 at 3:16 PM Ludovic Fernandez ***@***.***> wrote:
My current plan is to wait for the release of go1.22, based on the
previous Go release, this should happen in a few weeks (beginning of
February).
—
Reply to this email directly, view it on GitHub
<#4318 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKWAVHXHXLENUC7FHK7JYTYORRMRAVCNFSM6AAAAABBZWYBWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJRGEYDMNJZGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Theoretically, this bug is not directly related to Go1.22 but the current use case is only for Go1.22. Go1.22 (beta, RC, or GA) is currently not officially supported by golangci-lint. For now, I detected no breaking changes related to the upgrade to go1.22 but that was not the case with the previous versions of Go (changes inside golangci-lint and linters were required). Otherwise, if we create a release, we will have to create a minor version (because we already merged non-bugfix PRs), I would prefer this next minor be used to add the support of Go1.22. As a workaround, you can force the Go version inside the configuration: run:
go: 1.22 https://golangci-lint.run/usage/configuration/#run-configuration Kubernetes uses the "tools pattern" to install golangci-lint, another workaround is to use a commit instead of a tag. |
Welcome
Description of the problem
I am trying to convert kubernetes to use go workspaces. To do that I need Go 1.22rc. Go puts that string in all my go.mod files. golangci-lint barfs on it.
It looks like it assumes an int, but that isn't a correct assumption. Running gocritic standalone does not have this problem.
Version of golangci-lint
Configuration
Go environment
Verbose output of running
A minimal reproducible example or link to a public repository
Validation
The text was updated successfully, but these errors were encountered: