Skip to content

[release-4.13] OCPBUGS-82051: Drop github.com/distribution/distribution from go.mod#1305

Open
sunku5494 wants to merge 1 commit into
openshift:release-4.13from
sunku5494:rm-distribution-4.13
Open

[release-4.13] OCPBUGS-82051: Drop github.com/distribution/distribution from go.mod#1305
sunku5494 wants to merge 1 commit into
openshift:release-4.13from
sunku5494:rm-distribution-4.13

Conversation

@sunku5494
Copy link
Copy Markdown

The github.com/distribution/distribution dependency is not currently impacting our codebase. However, it is being removed as part of dependency hygiene to eliminate potential exposure to CVE-2026-35172.

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 20, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@sunku5494: This pull request references Jira Issue OCPBUGS-82051, 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-82051 to depend on a bug targeting a version in 4.14.0, 4.14.z 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.

Details

In response to this:

The github.com/distribution/distribution dependency is not currently impacting our codebase. However, it is being removed as part of dependency hygiene to eliminate potential exposure to CVE-2026-35172.

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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 20, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 9072666f-9206-460a-a9c7-c6ffff5da31f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from oceanc80 and perdasilva May 20, 2026 14:49
@sunku5494 sunku5494 force-pushed the rm-distribution-4.13 branch from 6e3459a to 51250a4 Compare May 20, 2026 14:51
@perdasilva
Copy link
Copy Markdown
Contributor

/retest

@tmshort
Copy link
Copy Markdown
Contributor

tmshort commented May 21, 2026

/lgtm
/approve
Pending CI completion

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 21, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 21, 2026

[APPROVALNOTIFIER] This PR is APPROVED

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

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 21, 2026
@tmshort
Copy link
Copy Markdown
Contributor

tmshort commented May 21, 2026

/test verify
/test e2e-gcp-olm

@grokspawn
Copy link
Copy Markdown
Contributor

/override ci/prow/verify

Failing because there is not an override-able mechanism for scripts in this release to allow staging changes in downstream-only PRs like this.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 26, 2026

@grokspawn: Overrode contexts on behalf of grokspawn: ci/prow/verify

Details

In response to this:

/override ci/prow/verify

Failing because there is not an override-able mechanism for scripts in this release to allow staging changes in downstream-only PRs like this.

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.

@kevinrizza
Copy link
Copy Markdown
Member

/label backport-risk-assessed

@kevinrizza
Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@kevinrizza: This pull request references Jira Issue OCPBUGS-82051, which is invalid:

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

Details

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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 26, 2026

@kevinrizza: The label(s) backport-risk-assessed cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: openshift-patch-managers, openshift-release-oversight, openshift-staff-engineers, openshift-sustaining-engineers

Details

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.

@perdasilva
Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@perdasilva: This pull request references Jira Issue OCPBUGS-82051, which is invalid:

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

Details

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.

The github.com/distribution/distribution dependency is not currently
impacting our codebase. However, it is being removed as part of dependency
hygiene to eliminate potential exposure to CVE-2026-35172.

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 1991a8f3756f884f1a715c871f9ed838e193a63e

Signed-off-by: Venkata Charan Sunku <vsunku@redhat.com>
@sunku5494 sunku5494 force-pushed the rm-distribution-4.13 branch from 51250a4 to 3cfd6df Compare May 29, 2026 16:13
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label May 29, 2026
@sunku5494
Copy link
Copy Markdown
Author

/test e2e-upgrade

@grokspawn
Copy link
Copy Markdown
Contributor

/retest-required

@grokspawn
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 29, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 29, 2026

@sunku5494: The following test 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-upgrade 3cfd6df link true /test e2e-upgrade

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants