🌱 Bump github.com/distribution/reference from 0.5.0 to 0.6.0

[prashantrewar]

What this PR does / why we need it:
Bumps github.com/distribution/reference from 0.5.0 to 0.6.0.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #10351

[k8s-ci-robot]

Welcome @prashantrewar!

It looks like this is your first PR to kubernetes-sigs/cluster-api 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @prashantrewar. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign neolit123 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[neolit123]

/area dependency
/ok-to-test

[chrischdi]

Requires a make generate-modules

also: fixes for the failing tests.

[sbueringer]

That is strange. That's something the bot already did on the dependabot PR
(maybe we actually have to run it twice? o.O)

[prashantrewar]

/test pull-cluster-api-test-main

[k8s-ci-robot]

@prashantrewar: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-test-main	4f44cfb	link	true	/test pull-cluster-api-test-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

[chrischdi]

I think the generate-modules came from:

• 🌱 Bump golang to v1.21.9 and golang.org/x/net to mitigate CVE-2023-45288 #10375

[prashantrewar]

I think the generate-modules came from:

• 🌱 Bump golang to v1.21.9 and golang.org/x/net to mitigate CVE-2023-45288 #10375

@chrischdi, I apologize but I didn't get this.

[chrischdi]

I think the generate-modules came from:

• 🌱 Bump golang to v1.21.9 and golang.org/x/net to mitigate CVE-2023-45288 #10375

@chrischdi, I apologize but I didn't get this.

The reason that you had to run make generate-modules to fix go.mod files was that the above PR merged to main.

What's still left for this PR is to take a look on why the tests at https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api/10373/pull-cluster-api-test-main/1775860189065383936 fail and fix them.

[k8s-ci-robot]

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/test-infra repository.

[sbueringer]

@chrischdi do you have time to take this one over?
We should bump ASAP

[sbueringer]

@prashantrewar Are you planning to work on this?

[chrischdi]

/close in favor of #10501

[chrischdi]

/close

[k8s-ci-robot]

@chrischdi: Closed this PR.

In response to this:

/close

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/test-infra repository.