openshift / ocp-release-operator-sdk

Apache License 2.0
16 stars 38 forks source link

[release-4.12] OCPBUGS-27618,OCPBUGS-27638,OCPBUGS-27643,OCPBUGS-27533,OCPBUGS-27553,OCPBUGS-27558: bump github.com/go-git/go-git/v5 to v5.11.0 #369

Closed oceanc80 closed 7 months ago

oceanc80 commented 8 months ago

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:

openshift-ci-robot commented 8 months ago

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

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-27638, which is invalid:

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-27643, which is invalid:

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-27533, which is invalid:

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-27553, which is invalid:

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-27558, which is invalid:

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/369): > > >**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.
openshift-ci-robot commented 8 months ago

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

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-27638, which is invalid:

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-27643, which is invalid:

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-27533, which is invalid:

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-27553, which is invalid:

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-27558, which is invalid:

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/369): > > >**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 commented 8 months ago

/label backport-risk-assessed

oceanc80 commented 8 months ago

/test unit

openshift-ci[bot] commented 8 months ago

@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 d7a8ad8028332fde064a5d5a491551ca5a49645a link true /test e2e-helm
ci/prow/images d7a8ad8028332fde064a5d5a491551ca5a49645a link true /test images
ci/prow/e2e-ansible d7a8ad8028332fde064a5d5a491551ca5a49645a link true /test e2e-ansible
ci/prow/sanity d7a8ad8028332fde064a5d5a491551ca5a49645a link true /test sanity
ci/prow/unit d7a8ad8028332fde064a5d5a491551ca5a49645a link true /test unit

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).
KeenonLee commented 8 months ago

https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/ginkgo-test-vm/52854/testReport/ Pre-merge testing LGTM

oceanc80 commented 7 months ago

/jira refresh

openshift-ci-robot commented 7 months ago

@oceanc80: This pull request references Jira Issue OCPBUGS-27618, 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.12.z) matches configured target version for branch (4.12.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27619](https://issues.redhat.com//browse/OCPBUGS-27619) 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-27619](https://issues.redhat.com//browse/OCPBUGS-27619) targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.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-27638, 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.12.z) matches configured target version for branch (4.12.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27639](https://issues.redhat.com//browse/OCPBUGS-27639) 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-27639](https://issues.redhat.com//browse/OCPBUGS-27639) targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.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-27643, 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.12.z) matches configured target version for branch (4.12.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27644](https://issues.redhat.com//browse/OCPBUGS-27644) 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-27644](https://issues.redhat.com//browse/OCPBUGS-27644) targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.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-27533, 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.12.z) matches configured target version for branch (4.12.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27534](https://issues.redhat.com//browse/OCPBUGS-27534) 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-27534](https://issues.redhat.com//browse/OCPBUGS-27534) targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.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-27553, 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.12.z) matches configured target version for branch (4.12.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27554](https://issues.redhat.com//browse/OCPBUGS-27554) 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-27554](https://issues.redhat.com//browse/OCPBUGS-27554) targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.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-27558, 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.12.z) matches configured target version for branch (4.12.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27559](https://issues.redhat.com//browse/OCPBUGS-27559) 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-27559](https://issues.redhat.com//browse/OCPBUGS-27559) targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.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/369#issuecomment-1927070929): >/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.
perdasilva commented 7 months ago

/lgtm

openshift-ci[bot] commented 7 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, 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.12/OWNERS)~~ [everettraven,oceanc80] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci-robot commented 7 months ago

@oceanc80: Jira Issue OCPBUGS-27618: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-27618 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-27638: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-27638 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-27643: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-27643 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-27533: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-27533 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-27553: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-27553 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-27558: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-27558 has been moved to the MODIFIED state.

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/369): > > >**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.
openshift-bot commented 7 months ago

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-helm-operator-container-v4.12.0-202402051438.p0.g0bd975e.assembly.stream for distgit openshift-enterprise-helm-operator. All builds following this will include this PR.