Skip to content

update test/tools vendor and ginkgo #25560

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Luap99
Copy link
Member

@Luap99 Luap99 commented Mar 12, 2025

Does this PR introduce a user-facing change?

None

Copy link
Contributor

openshift-ci bot commented Mar 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 12, 2025
Luap99 added 2 commits March 13, 2025 11:49
Update the tools to the latest version. Add a note that go-swagger
cannot be updated to v0.31.0 to due go checksum mismatch.

Signed-off-by: Paul Holzinger <[email protected]>
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 23, 2025
@openshift-merge-robot
Copy link
Collaborator

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@@ -53,7 +53,7 @@ require (
github.com/moby/sys/user v0.3.0
github.com/moby/term v0.5.2
github.com/nxadm/tail v1.4.11
github.com/onsi/ginkgo/v2 v2.22.2
github.com/onsi/ginkgo/v2 v2.23.0
Copy link
Contributor

Choose a reason for hiding this comment

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

In view of commit 6df50be, this needs to be updated to v2.23.3

(ideally, renovate should be configured to bump ginkgo in both places at once)

Copy link
Contributor

Choose a reason for hiding this comment

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

The alternative is to drop this second copy entirely: #25732

Copy link
Member Author

Choose a reason for hiding this comment

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

(ideally, renovate should be configured to bump ginkgo in both places at once)

It does, but it doesn't work when ginkgo gets updated due transitive updates, i.e. from c/common.

Copy link

github-actions bot commented May 1, 2025

A friendly reminder that this PR had no activity for 30 days.

@kolyshkin
Copy link
Contributor

@Luap99 afaics this PR is obsoleted by #25732 and recent renovate PRs and should be closed.

@Luap99
Copy link
Member Author

Luap99 commented May 2, 2025

@Luap99 afaics this PR is obsoleted by #25732 and recent renovate PRs and should be closed.

That only changed ginkgo not the other deps.
The issue here is that we got into a situation where go-swagger cannot be updated as it breaks once go.mod is updated to go 1.23 (go-swagger/go-swagger#3131) and thus we cannot update the other tools since they now depend on go 1.23. So overall I would say this is a quite bad situation as we seem to be using unmaintained tooling.

I don't know the cards but I believe someone is lookup into swagger alternatives (or ways to improve swagger)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note-none stale-pr
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants