Skip to content

Conversation

@dnwe
Copy link

@dnwe dnwe commented Jan 24, 2025

Setting the go directive to 1.23.0 requires all consumers of the module
to be building with 1.23.0 or newer release of Go 1.23 and to update
their own go.mod accordingly — this seems unnecessarily restrictive for
a library module, particularly as the code itself doesn't currently use
any modern language constructs and builds fine even with older Go
versions.

Instead set the go directive to 1.22.0 and use the toolchain directive
to recommend the latest 1.23.x when building locally.

Note: this also includes a run of hack/bump-deps.sh to ensure all deps
are compatible with go1.22.0 as well

Fixes #2045

dnwe added 2 commits January 24, 2025 09:32
Setting the go directive to 1.23.0 requires all consumers of the module
to be building with 1.23.0 or newer release of Go 1.23 and to update
their own go.mod accordingly — this seems unnecessarily restrictive for
a library module, particularly as the code itself doesn't currently use
any modern language constructs and builds fine even with older Go
versions.

Instead set the go directive to 1.22.0 and use the toolchain directive
to recommend the latest 1.23.x when building locally.

Note: this also includes a run of `hack/bump-deps.sh` to ensure all deps
are compatible with go1.22.0 as well

Fixes google#2045

Signed-off-by: Dominic Evans <[email protected]>
Ensure that the go and toolchain directives in go.mod are kept in sync
and pinned at the desired support level (N-1 and N)

Note, we are also pinning k8s.io packages to an explicit v0.31.5 version
in the pkg/authn go.mod files in order to avoid prerelease versions that
`go get -u` will pickup.

Signed-off-by: Dominic Evans <[email protected]>
@dnwe
Copy link
Author

dnwe commented Jan 30, 2025

@imjasonh would you be happy to take a look at this PR?

@haydentherapper
Copy link

@imjasonh @jonjohnsonjr Bumping this PR for review, this is needed for us to stay on Go 1.22 in sigstore.

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.

question: what is the Go version support policy?

2 participants