You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That change was introduced in this commit: 7cd04d1
The project is set up to be built and tested with Go 1.23.1. It is recommended to use this version to ensure compatibility and avoid potential issues.
As the documentation says:
Each major Go release is supported until there are two newer major releases. For example, Go 1.5 was supported until the Go 1.7 release, and Go 1.6 was supported until the Go 1.8 release. We fix critical problems, including critical security problems, in supported releases as needed by issuing minor revisions (for example, Go 1.6.1, Go 1.6.2, and so on).
The Major Go release 1.22 must be supported because the 1.24 is still a release candidate.
Steps to reproduce it:
➜ brokerapi git:(main) ✗ gvm use go1.22.10
Now using version go1.22.10
➜ brokerapi git:(main) ✗ GOTOOLCHAIN=local
➜ brokerapi git:(main) ✗ go mod download
go: module github.com/maxbrunsfeld/counterfeiter/[email protected] requires go >= 1.23; switching to go1.23.4
The text was updated successfully, but these errors were encountered:
It looks like this PR introduced code that will only work when using go 1.23. We could explore using a build tags to solve for this, however given the proximity to the go 1.24 release I am unlikely to spend the time to do this myself. PR welcome.
In the interim, please use v6.9.0, which should still work with 1.22.
When using this sentence in the go.mod file:
toolchain go1.23.1
That change was introduced in this commit: 7cd04d1
The project is set up to be built and tested with Go 1.23.1. It is recommended to use this version to ensure compatibility and avoid potential issues.
As the documentation says:
The Major Go release 1.22 must be supported because the 1.24 is still a release candidate.
Steps to reproduce it:
The text was updated successfully, but these errors were encountered: