OCPBUGS-51598: bump golang.org/x/oauth2

[sbiradar10]

Bump to prevent CVE-2025-22868 . As we can't simply use the upstream package we are using the openshift's fork. We can't use the upstream because we don't have a go v1.23 builder for older openshift versions.

[openshift-ci-robot]

@sbiradar10: This pull request references Jira Issue OCPBUGS-51598, which is invalid:

• expected dependent Jira Issue OCPBUGS-51596 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Bump to prevent GHSA-3wqc-mwfx-672p. As we can't simply use the upstream package we are using the openshift's fork. We can't use the upstream because we don't have a go v1.23 builder for older openshift versions.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sbiradar10
Once this PR has been reviewed and has the lgtm label, please assign bparees for approval. For more information see the 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

[sbiradar10]

/retest e2e-aws-ovn-upgrade

[openshift-ci]

@sbiradar10: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test e2e-aws-operator

/test e2e-aws-ovn

/test e2e-aws-ovn-image-registry

/test e2e-aws-ovn-upgrade

/test e2e-hypershift

/test e2e-hypershift-conformance

/test e2e-vsphere-operator

/test images

/test unit

/test verify

The following commands are available to trigger optional jobs:

/test e2e-azure-manual-oidc

/test e2e-azure-operator

/test e2e-azure-ovn

/test e2e-gcp-operator

/test e2e-gcp-ovn

/test e2e-openstack

/test e2e-vsphere

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-cluster-image-registry-operator-release-4.14-e2e-aws-operator

pull-ci-openshift-cluster-image-registry-operator-release-4.14-e2e-aws-ovn

pull-ci-openshift-cluster-image-registry-operator-release-4.14-e2e-aws-ovn-image-registry

pull-ci-openshift-cluster-image-registry-operator-release-4.14-e2e-aws-ovn-upgrade

pull-ci-openshift-cluster-image-registry-operator-release-4.14-e2e-gcp-operator

pull-ci-openshift-cluster-image-registry-operator-release-4.14-e2e-gcp-ovn

pull-ci-openshift-cluster-image-registry-operator-release-4.14-e2e-hypershift

pull-ci-openshift-cluster-image-registry-operator-release-4.14-e2e-hypershift-conformance

pull-ci-openshift-cluster-image-registry-operator-release-4.14-images

pull-ci-openshift-cluster-image-registry-operator-release-4.14-unit

pull-ci-openshift-cluster-image-registry-operator-release-4.14-verify

In response to this:

/retest e2e-aws-ovn-upgrade

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.

[sbiradar10]

/test e2e-aws-ovn-upgrade

[flavianmissi]

/retest-required

[openshift-ci]

@sbiradar10: all tests passed!

Full PR test history. Your PR dashboard.

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

[xiuwang]

/label qe-approved
/label cherry-pick-approved

[openshift-ci-robot]

@sbiradar10: This pull request references Jira Issue OCPBUGS-51598, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-51596 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-51596 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

Bump to prevent CVE-2025-22868 . As we can't simply use the upstream package we are using the openshift's fork. We can't use the upstream because we don't have a go v1.23 builder for older openshift versions.

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 openshift-eng/jira-lifecycle-plugin repository.