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.

Sign up for GitHub

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

Jump to bottom

Downgrade Go version inside `go.mod` #33

Closed

ldez opened this issue Mar 18, 2024 · 3 comments · Fixed by #34

Contributor

ldez commented Mar 18, 2024

Is it possible for you to downgrade the version inside your go.mod to go1.21?

The new way to handle the module and Go version is strict.

The Go version inside the go.mod defines the minimum supported version of Go, and forces the users to follow this minimum version.

You can compile with a higher version than the go.mod but you cannot compile with a version lower than the go.mod.

https://go.dev/blog/toolchain

golangci/golangci-lint#4529

Note: golang.org/x/tools@v0.19.0 contains a bug golang/go#66259

The text was updated successfully, but these errors were encountered:

ldez mentioned this issue

build(deps): bump github.com/alexkohler/nakedret/v2 from 2.0.2 to 2.0.3 golangci/golangci-lint#4529

Closed

alexkohler mentioned this issue

[chore] Bump down go.mod version to 1.21 #34

Merged

alexkohler closed this as completed in #34

Owner

alexkohler commented Mar 19, 2024

Sure thing - apologies for the inconvenience!

Contributor Author

ldez commented Mar 19, 2024 •

edited

@alexkohler Can you create a new tag?

You cannot re-use an existing tag (v2.0.3), the go proxies will report a checksum mismatch.

SECURITY ERROR
This download does NOT match the one reported by the checksum server.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

Owner

alexkohler commented Mar 19, 2024

Done. Just pushed a v2.0.4 tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment