🌱 Update go-github from v33.0.0 to v45.2.0

[oscr]

This pr updates go-github from v33.0.0 to v45.2.0.

For reference: https://github.com/google/go-github/releases

Related issue #6687

[k8s-ci-robot]

Hi @oscr. 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.

[killianmuldoon]

/ok-to-test

[sbueringer]

/test pull-cluster-api-e2e-full-main

Thx!

/lgtm

I would not cherry-pick it back into the 1.2 branch just because it's a bump of 12 major versions and I would prefer more time to see if it breaks something.

[oscr]

@sbueringer I agree 100%.

[chrischdi]

/lgtm

[fabriziopandini]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

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 [fabriziopandini]

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

[fabriziopandini]

@sbueringer let's consider to cherry pick on 1.2 so we can get some feedback from folks validating the release

[sbueringer]

Good point. You're right, we won't really get a lot of feedback from the change just being on main (mostly from CI, but we already have enough CI feedback already).

For me it would be fine to cherry-pick as we still have some time to go and we expect infra providers to actively test our beta release

Also the dependency is only used in clusterctl so the blast radius is limited

[sbueringer]

/cherry-pick release-1.2

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #6723

In response to this:

/cherry-pick release-1.2

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.