OCPBUGS-50830, OCPBUGS-50832, OCPBUGS-50836: Bump github.com/distribution/distribution/v3 #965

tmshort · 2025-02-28T17:13:47Z

Bumps github.com/distribution/distribution/v3 from 3.0.0-rc.2 to 3.0.0-rc.3.

updated-dependencies:

dependency-name: github.com/distribution/distribution/v3 dependency-type: direct:production update-type: version-update:semver-patch ...

Upstream-repository: operator-registry
Upstream-commit: b7c42a0b8271c185f2e562c05b7344689c161002 (cherry picked from commit ecc1251)

openshift-ci-robot · 2025-02-28T17:13:54Z

@tmshort: This pull request references Jira Issue OCPBUGS-50830, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-50830 to depend on a bug targeting a version in 4.19.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-50832 to depend on a bug targeting a version in 4.19.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-50836 to depend on a bug targeting a version in 4.19.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

Bumps github.com/distribution/distribution/v3 from 3.0.0-rc.2 to 3.0.0-rc.3.

Release notes

Commits

updated-dependencies:

dependency-name: github.com/distribution/distribution/v3 dependency-type: direct:production update-type: version-update:semver-patch ...

Upstream-repository: operator-registry
Upstream-commit: b7c42a0b8271c185f2e562c05b7344689c161002 (cherry picked from commit ecc1251)

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.

tmshort · 2025-02-28T18:38:56Z

/jira refresh

openshift-ci-robot · 2025-02-28T18:39:03Z

@tmshort: This pull request references Jira Issue OCPBUGS-50830, which is invalid:

expected dependent Jira Issue OCPBUGS-52182 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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-50832, which is invalid:

expected dependent Jira Issue OCPBUGS-52182 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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-50836, which is invalid:

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

/jira refresh

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.

Bumps [github.com/distribution/distribution/v3](https://github.com/distribution/distribution) from 3.0.0-rc.2 to 3.0.0-rc.3. - [Release notes](https://github.com/distribution/distribution/releases) - [Commits](distribution/distribution@v3.0.0-rc.2...v3.0.0-rc.3) --- updated-dependencies: - dependency-name: github.com/distribution/distribution/v3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Upstream-repository: operator-registry Upstream-commit: b7c42a0b8271c185f2e562c05b7344689c161002 (cherry picked from commit ecc1251) Signed-off-by: Todd Short <[email protected]>

tmshort · 2025-02-28T18:47:29Z

/jira refresh

openshift-ci-robot · 2025-02-28T18:47:35Z

@tmshort: This pull request references Jira Issue OCPBUGS-50830, which is invalid:

expected dependent Jira Issue OCPBUGS-52182 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.

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

expected dependent Jira Issue OCPBUGS-52182 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.

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

expected dependent Jira Issue OCPBUGS-52182 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.

In response to this:

/jira refresh

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 · 2025-02-28T22:03:38Z

@tmshort: 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.

camilamacedo86 · 2025-03-03T09:08:27Z

HI @tmshort

Bumps github.com/distribution/distribution/v3 from 3.0.0-rc.2 to 3.0.0-rc.3.

Did we not done it in upstream projects?
Why do we need to bump here directly?

camilamacedo86 · 2025-03-03T09:16:18Z

go.mod

@@ -1,6 +1,6 @@
 module github.com/openshift/operator-framework-olm

-go 1.22.5
+go 1.22.7


@tmshort Why we are updating the golang version?

It's required by the distribution update.
This is OK, because release-4.18 uses 1.22.9.

See
https://github.com/distribution/distribution/blob/1b01625dae6a0a6321dadde7a30d0c3b92093a3e/go.mod#L3

OH I see 👍

camilamacedo86 · 2025-03-03T09:17:08Z

/lgtm cancel
/approve cancel

Until we get the answers. Sorry

tmshort · 2025-03-03T19:08:53Z

/jira refresh

openshift-ci-robot · 2025-03-03T19:09:08Z

@tmshort: This pull request references Jira Issue OCPBUGS-50830, 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.18.z) matches configured target version for branch (4.18.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52182 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-52182 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

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

This pull request references Jira Issue OCPBUGS-50832, 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.18.z) matches configured target version for branch (4.18.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52182 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-52182 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

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

This pull request references Jira Issue OCPBUGS-50836, 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.18.z) matches configured target version for branch (4.18.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52182 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-52182 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

In response to this:

/jira refresh

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.

camilamacedo86 · 2025-03-03T19:36:39Z

/lgtm
/approve

openshift-ci · 2025-03-03T19:37:06Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, tmshort

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:

~~DOWNSTREAM_OWNERS~~ [tmshort]

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

bandrade · 2025-03-03T21:07:02Z

/label cherry-pick-approved

Xia-Zhao-rh · 2025-03-04T03:08:42Z

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

openshift-ci-robot · 2025-03-04T03:08:55Z

@tmshort: This pull request references Jira Issue OCPBUGS-50830, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.18.z) matches configured target version for branch (4.18.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52182 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-52182 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

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

This pull request references Jira Issue OCPBUGS-50832, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.18.z) matches configured target version for branch (4.18.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52182 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-52182 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

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

This pull request references Jira Issue OCPBUGS-50836, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.18.z) matches configured target version for branch (4.18.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52182 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-52182 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

In response to this:

Bumps github.com/distribution/distribution/v3 from 3.0.0-rc.2 to 3.0.0-rc.3.

Release notes

Commits

updated-dependencies:

dependency-name: github.com/distribution/distribution/v3 dependency-type: direct:production update-type: version-update:semver-patch ...

Upstream-repository: operator-registry
Upstream-commit: b7c42a0b8271c185f2e562c05b7344689c161002 (cherry picked from commit ecc1251)

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.

tmshort · 2025-03-04T14:13:34Z

/label backport-risk-assessed

openshift-ci · 2025-03-04T14:13:52Z

@tmshort: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/label backport-risk-assessed

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.

oceanc80 · 2025-03-04T14:46:22Z

/label backport-risk-assessed

openshift-ci-robot · 2025-03-04T14:48:57Z

@tmshort: Jira Issue OCPBUGS-50830: All pull requests linked via external trackers have merged:

openshift/operator-framework-olm#965

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

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

openshift/operator-framework-olm#965

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

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

openshift/operator-framework-olm#965

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

In response to this:

Bumps github.com/distribution/distribution/v3 from 3.0.0-rc.2 to 3.0.0-rc.3.

Release notes

Commits

updated-dependencies:

dependency-name: github.com/distribution/distribution/v3 dependency-type: direct:production update-type: version-update:semver-patch ...

Upstream-repository: operator-registry
Upstream-commit: b7c42a0b8271c185f2e562c05b7344689c161002 (cherry picked from commit ecc1251)

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-bot · 2025-03-04T16:41:31Z

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.18.0-202503041603.p0.g877b6fd.assembly.stream.el9.
All builds following this will include this PR.

openshift-bot · 2025-03-04T16:44:30Z

[ART PR BUILD NOTIFIER]

Distgit: operator-registry
This PR has been included in build operator-registry-container-v4.18.0-202503041603.p0.g877b6fd.assembly.stream.el9.
All builds following this will include this PR.

openshift-bot · 2025-03-04T16:47:32Z

[ART PR BUILD NOTIFIER]

Distgit: ose-operator-framework-tools
This PR has been included in build ose-operator-framework-tools-container-v4.18.0-202503041603.p0.g877b6fd.assembly.stream.el9.
All builds following this will include this PR.

openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Feb 28, 2025

openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Feb 28, 2025

tmshort changed the title ~~OCPBUGS-50830, OCPBUGS-50832, OCPBUGS-50836: Bump github.com/distribution/distribution/v3 (#1580)~~ OCPBUGS-50830, OCPBUGS-50832, OCPBUGS-50836: Bump github.com/distribution/distribution/v3 Feb 28, 2025

openshift-ci bot requested review from joelanford and oceanc80 February 28, 2025 17:14

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 28, 2025

tmshort force-pushed the update-distrib-4.18 branch from 646e9fe to e31a86b Compare February 28, 2025 18:45

This comment was marked as outdated.

Sign in to view

openshift-ci bot assigned camilamacedo86 Mar 3, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2025

camilamacedo86 reviewed Mar 3, 2025

View reviewed changes

openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2025

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 3, 2025

openshift-ci bot requested a review from Xia-Zhao-rh March 3, 2025 19:09

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2025

openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Mar 3, 2025

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Mar 4, 2025

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 4, 2025

openshift-ci bot assigned bandrade, emmajiafan, jianzhangbjz, KeenonLee, kuiwang02 and Xia-Zhao-rh Mar 4, 2025

openshift-merge-bot bot merged commit 877b6fd into openshift:release-4.18 Mar 4, 2025
14 checks passed

tmshort deleted the update-distrib-4.18 branch March 4, 2025 14:57

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

OCPBUGS-50830, OCPBUGS-50832, OCPBUGS-50836: Bump github.com/distribution/distribution/v3 #965

OCPBUGS-50830, OCPBUGS-50832, OCPBUGS-50836: Bump github.com/distribution/distribution/v3 #965

tmshort commented Feb 28, 2025

openshift-ci-robot commented Feb 28, 2025

tmshort commented Feb 28, 2025

openshift-ci-robot commented Feb 28, 2025

tmshort commented Feb 28, 2025

openshift-ci-robot commented Feb 28, 2025

openshift-ci bot commented Feb 28, 2025

This comment was marked as outdated.

camilamacedo86 commented Mar 3, 2025

camilamacedo86 Mar 3, 2025

tmshort Mar 3, 2025

tmshort Mar 3, 2025

camilamacedo86 Mar 3, 2025

camilamacedo86 commented Mar 3, 2025

tmshort commented Mar 3, 2025

openshift-ci-robot commented Mar 3, 2025

camilamacedo86 commented Mar 3, 2025

openshift-ci bot commented Mar 3, 2025

bandrade commented Mar 3, 2025

Xia-Zhao-rh commented Mar 4, 2025

openshift-ci-robot commented Mar 4, 2025

tmshort commented Mar 4, 2025

openshift-ci bot commented Mar 4, 2025

oceanc80 commented Mar 4, 2025

openshift-ci-robot commented Mar 4, 2025

openshift-bot commented Mar 4, 2025

openshift-bot commented Mar 4, 2025

openshift-bot commented Mar 4, 2025

OCPBUGS-50830, OCPBUGS-50832, OCPBUGS-50836: Bump github.com/distribution/distribution/v3 #965

OCPBUGS-50830, OCPBUGS-50832, OCPBUGS-50836: Bump github.com/distribution/distribution/v3 #965

Conversation

tmshort commented Feb 28, 2025

openshift-ci-robot commented Feb 28, 2025

tmshort commented Feb 28, 2025

openshift-ci-robot commented Feb 28, 2025

tmshort commented Feb 28, 2025

openshift-ci-robot commented Feb 28, 2025

openshift-ci bot commented Feb 28, 2025

This comment was marked as outdated.

camilamacedo86 commented Mar 3, 2025

camilamacedo86 Mar 3, 2025

Choose a reason for hiding this comment

tmshort Mar 3, 2025

Choose a reason for hiding this comment

tmshort Mar 3, 2025

Choose a reason for hiding this comment

camilamacedo86 Mar 3, 2025

Choose a reason for hiding this comment

camilamacedo86 commented Mar 3, 2025

tmshort commented Mar 3, 2025

openshift-ci-robot commented Mar 3, 2025

camilamacedo86 commented Mar 3, 2025

openshift-ci bot commented Mar 3, 2025

bandrade commented Mar 3, 2025

Xia-Zhao-rh commented Mar 4, 2025

openshift-ci-robot commented Mar 4, 2025

tmshort commented Mar 4, 2025

openshift-ci bot commented Mar 4, 2025

oceanc80 commented Mar 4, 2025

openshift-ci-robot commented Mar 4, 2025

openshift-bot commented Mar 4, 2025

openshift-bot commented Mar 4, 2025

openshift-bot commented Mar 4, 2025