[release-4.11] OCPBUGS-27617,OCPBUGS-27637,OCPBUGS-27642,OCPBUGS-27532,OCPBUGS-27552,OCPBUGS-27557: bump github.com/go-git/go-git/v5 to v5.11.0

[oceanc80]

Description of the change: This is a cherry-pick of https://github.com/openshift/ocp-release-operator-sdk/pull/364

Motivation for the change: Addresses the following CVEs:

https://github.com/advisories/GHSA-mw99-9chc-xw7r https://github.com/advisories/GHSA-449p-3h89-pw88

Checklist

If the pull request includes user-facing changes, extra documentation is required:

• [ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
• [ ] Add or update relevant sections of the docs website in website/content/en/docs

[openshift-ci-robot]

@oceanc80: This pull request references Jira Issue OCPBUGS-27617, which is invalid:

• expected dependent Jira Issue OCPBUGS-27618 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

This pull request references Jira Issue OCPBUGS-27637, which is invalid:

• expected dependent Jira Issue OCPBUGS-27638 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

This pull request references Jira Issue OCPBUGS-27642, which is invalid:

• expected dependent Jira Issue OCPBUGS-27643 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

This pull request references Jira Issue OCPBUGS-27532, which is invalid:

• expected dependent Jira Issue OCPBUGS-27533 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

This pull request references Jira Issue OCPBUGS-27552, which is invalid:

• expected dependent Jira Issue OCPBUGS-27553 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

This pull request references Jira Issue OCPBUGS-27557, which is invalid:

• expected dependent Jira Issue OCPBUGS-27558 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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](https://github.com/openshift/ocp-release-operator-sdk/pull/370): > > >**Description of the change:** >This is a cherry-pick of https://github.com/openshift/ocp-release-operator-sdk/pull/364 > >**Motivation for the change:** >Addresses the following CVEs: > >https://github.com/advisories/GHSA-mw99-9chc-xw7r >https://github.com/advisories/GHSA-449p-3h89-pw88 > >**Checklist** > >If the pull request includes user-facing changes, extra documentation is required: >- [ ] Add a new changelog fragment in `changelog/fragments` (see [`changelog/fragments/00-template.yaml`](https://github.com/operator-framework/operator-sdk/tree/master/changelog/fragments/00-template.yaml)) >- [ ] Add or update relevant sections of the docs website in [`website/content/en/docs`](https://github.com/operator-framework/operator-sdk/tree/master/website/content/en/docs) > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Focp-release-operator-sdk). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[oceanc80]

/label backport-risk-assessed

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: oceanc80

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](https://github.com/openshift/ocp-release-operator-sdk/blob/release-4.11/OWNERS)~~ [oceanc80] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[oceanc80]

/retest-required

[oceanc80]

/jira refresh

[openshift-ci-robot]

@oceanc80: This pull request references Jira Issue OCPBUGS-27617, which is invalid:

• expected dependent Jira Issue OCPBUGS-27618 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

This pull request references Jira Issue OCPBUGS-27637, which is invalid:

• expected dependent Jira Issue OCPBUGS-27638 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

This pull request references Jira Issue OCPBUGS-27642, which is invalid:

• expected dependent Jira Issue OCPBUGS-27643 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

This pull request references Jira Issue OCPBUGS-27532, which is invalid:

• expected dependent Jira Issue OCPBUGS-27533 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

This pull request references Jira Issue OCPBUGS-27552, which is invalid:

• expected dependent Jira Issue OCPBUGS-27553 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

This pull request references Jira Issue OCPBUGS-27557, which is invalid:

• expected dependent Jira Issue OCPBUGS-27558 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/370#issuecomment-1928137163): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Focp-release-operator-sdk). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-ci[bot]]

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

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-helm	5eb2cd2cc6372cdc171f7cccef12096211c26365	link	true	/test e2e-helm
ci/prow/sanity	5eb2cd2cc6372cdc171f7cccef12096211c26365	link	true	/test sanity
ci/prow/unit	5eb2cd2cc6372cdc171f7cccef12096211c26365	link	true	/test unit
ci/prow/e2e-ansible	5eb2cd2cc6372cdc171f7cccef12096211c26365	link	true	/test e2e-ansible
ci/prow/images	5eb2cd2cc6372cdc171f7cccef12096211c26365	link	true	/test images

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[oceanc80]

/jira refresh

[openshift-ci-robot]

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

6 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.11.z) matches configured target version for branch (4.11.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27618](https://issues.redhat.com//browse/OCPBUGS-27618) 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-27618](https://issues.redhat.com//browse/OCPBUGS-27618) targets the "4.12.z" version, which is one of the valid target versions: 4.12.0, 4.12.z * bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jfan@redhat.com), skipping review request.

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

6 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.11.z) matches configured target version for branch (4.11.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27638](https://issues.redhat.com//browse/OCPBUGS-27638) 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-27638](https://issues.redhat.com//browse/OCPBUGS-27638) targets the "4.12.z" version, which is one of the valid target versions: 4.12.0, 4.12.z * bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jfan@redhat.com), skipping review request.

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

6 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.11.z) matches configured target version for branch (4.11.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27643](https://issues.redhat.com//browse/OCPBUGS-27643) 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-27643](https://issues.redhat.com//browse/OCPBUGS-27643) targets the "4.12.z" version, which is one of the valid target versions: 4.12.0, 4.12.z * bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jfan@redhat.com), skipping review request.

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

6 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.11.z) matches configured target version for branch (4.11.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27533](https://issues.redhat.com//browse/OCPBUGS-27533) 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-27533](https://issues.redhat.com//browse/OCPBUGS-27533) targets the "4.12.z" version, which is one of the valid target versions: 4.12.0, 4.12.z * bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jfan@redhat.com), skipping review request.

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

6 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.11.z) matches configured target version for branch (4.11.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27553](https://issues.redhat.com//browse/OCPBUGS-27553) 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-27553](https://issues.redhat.com//browse/OCPBUGS-27553) targets the "4.12.z" version, which is one of the valid target versions: 4.12.0, 4.12.z * bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jfan@redhat.com), skipping review request.

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

6 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.11.z) matches configured target version for branch (4.11.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27558](https://issues.redhat.com//browse/OCPBUGS-27558) 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-27558](https://issues.redhat.com//browse/OCPBUGS-27558) targets the "4.12.z" version, which is one of the valid target versions: 4.12.0, 4.12.z * bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jfan@redhat.com), skipping review request.

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/370#issuecomment-1929751274): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Focp-release-operator-sdk). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-ci-robot]

@oceanc80: This pull request references Jira Issue OCPBUGS-27617. The bug has been updated to no longer refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-27637. The bug has been updated to no longer refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-27642. The bug has been updated to no longer refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-27532. The bug has been updated to no longer refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-27552. The bug has been updated to no longer refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-27557. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/370): > > >**Description of the change:** >This is a cherry-pick of https://github.com/openshift/ocp-release-operator-sdk/pull/364 > >**Motivation for the change:** >Addresses the following CVEs: > >https://github.com/advisories/GHSA-mw99-9chc-xw7r >https://github.com/advisories/GHSA-449p-3h89-pw88 > >**Checklist** > >If the pull request includes user-facing changes, extra documentation is required: >- [ ] Add a new changelog fragment in `changelog/fragments` (see [`changelog/fragments/00-template.yaml`](https://github.com/operator-framework/operator-sdk/tree/master/changelog/fragments/00-template.yaml)) >- [ ] Add or update relevant sections of the docs website in [`website/content/en/docs`](https://github.com/operator-framework/operator-sdk/tree/master/website/content/en/docs) > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Focp-release-operator-sdk). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.