Closed egibs closed 2 months ago
Just curious - was there a particular inspiration for this change?
I don't mind upgrading to the latest go version to use a feature, but upping the installation requirements otherwise might exclude some users.
Just curious - was there a particular inspiration for this change?
I don't mind upgrading to the latest go version to use a feature, but upping the installation requirements otherwise might exclude some users.
Good point. This isn't a necessity right now and it can always be re-opened later. I'll probably port the go-version-file
changes to another PR, though.
Less invasive PR: https://github.com/chainguard-dev/bincapz/pull/186
This PR updates from Go
1.21.6
to1.22
and also containsgo get -u
andgo mod tidy
changes.This PR also uses
go.mod
for thego-version-file
to make the CI setup steps easier to manage (rather than specifying1.22
for each of thesetup-go
versions).