Skip to content
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

chore: relax go directive to permit 1.22.x #927

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

dnwe
Copy link
Contributor

@dnwe dnwe commented Jan 17, 2025

Summary

Similar to sigstore/rekor#2323, relax the go.mod go directive to 1.22.0 here as well.

The go directive sets the minimum version of Go required to use this module. There's no need to set this to the latest semver patch version of a given Go release unless the semantics of that version of Go are required to build/test/use the module.

Ref: https://go.dev/ref/mod#go-mod-file-go

Release Note

NONE

Documentation

NONE

Similar to sigstore/rekor#2323, relax the go.mod go directive to 1.22.0
here as well.

The go directive sets the minimum version of Go required to use this
module. There's no need to set this to the latest semver patch version
of a given Go release unless the semantics of that version of Go are
required to build/test/use the module.

Ref: https://go.dev/ref/mod#go-mod-file-go

Signed-off-by: Dominic Evans <dominic.evans@uk.ibm.com>
@@ -37,7 +39,7 @@ require (
golang.org/x/net v0.34.0
google.golang.org/protobuf v1.36.3
gopkg.in/yaml.v3 v3.0.1
sigs.k8s.io/release-utils v0.9.0
sigs.k8s.io/release-utils v0.8.4
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fyi @cpanato since you maintain this - I looked into why release-utils had to bump to 1.23 and the culprit seems to be https://github.com/maxbrunsfeld/counterfeiter/, which I think could be trivially downgraded back to 1.22.

Copy link
Contributor Author

@dnwe dnwe Jan 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@haydentherapper i saw this one, but an issue had already been raised and the maintainer didn’t seem keen to cut a new release before 1.24, see here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More specifically, 1.23 type aliasing had been introduced into the code so a trivial downgrade wasn’t possible

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, I was nerdsniped into making a PR for counterfeiter here

Copy link

codecov bot commented Jan 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 44.73%. Comparing base (6fd19b0) to head (a66a8e0).
Report is 272 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #927      +/-   ##
==========================================
- Coverage   52.85%   44.73%   -8.12%     
==========================================
  Files          20       55      +35     
  Lines        1209     3657    +2448     
==========================================
+ Hits          639     1636     +997     
- Misses        509     1881    +1372     
- Partials       61      140      +79     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@haydentherapper haydentherapper merged commit 1d583aa into sigstore:main Jan 21, 2025
8 checks passed
@dnwe dnwe deleted the go-directive branch January 21, 2025 21:48
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.

2 participants