-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
go mod: no longer use 1.18 #19204
go mod: no longer use 1.18 #19204
Conversation
1.18 is EOL and we should not have to set this since the current versions should generate compatible go.sum files anyway. This is an attempt to fix broken renovate PRs which create a different go.sum and thus do not pass CI checks. Signed-off-by: Paul Holzinger <pholzing@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@flouthoc PTAL
I wonder if this may be the cause or if this is a bug in renovate. |
Actually I think there is something wrong with renovate: containers/common#1555 passed tests so I assumed it worked but if I now run make vendor locally I get a diff which means c/common CI is missing the diff check. Anyway this should be good to merge but I don't think it will fix renovate PRs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/approve
/lgtm
/hold
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flouthoc, Luap99, vrothberg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
1.18 is EOL and we should not have to set this since the current versions should generate compatible go.sum files anyway.
This is an attempt to fix broken renovate PRs which create a different go.sum and thus do not pass CI checks.
Does this PR introduce a user-facing change?