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

go mod: no longer use 1.18 #19204

Merged
merged 1 commit into from
Jul 12, 2023
Merged

Conversation

Luap99
Copy link
Member

@Luap99 Luap99 commented Jul 12, 2023

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?

None

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>
@openshift-ci openshift-ci bot added release-note-none approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 12, 2023
Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

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

LGTM
@flouthoc PTAL

@Luap99
Copy link
Member Author

Luap99 commented Jul 12, 2023

I wonder if this may be the cause or if this is a bug in renovate.

@Luap99
Copy link
Member Author

Luap99 commented Jul 12, 2023

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.

Copy link
Collaborator

@flouthoc flouthoc left a 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

@openshift-ci openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Jul 12, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 12, 2023

[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:
  • OWNERS [Luap99,flouthoc,vrothberg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Luap99
Copy link
Member Author

Luap99 commented Jul 12, 2023

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 12, 2023
@openshift-merge-robot openshift-merge-robot merged commit c5006f4 into containers:main Jul 12, 2023
@Luap99 Luap99 deleted the vendor-tidy branch July 12, 2023 10:27
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Oct 11, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note-none
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants