Skip to content

OCPBUGS-78280: [release-4.16] update go mod dependency for konflux#267

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.16from
fgallott:hermetic-4.16
Apr 3, 2026
Merged

OCPBUGS-78280: [release-4.16] update go mod dependency for konflux#267
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.16from
fgallott:hermetic-4.16

Conversation

@fgallott
Copy link
Copy Markdown

cherry pick of 6f4319a, #240

same as #266

@openshift-ci openshift-ci bot requested review from RadekManak and elmiko February 24, 2026 15:00
@fgallott fgallott changed the title UPSTREAM: <carry>: update go mod dependency for konflux [release-4.16] update go mod dependency for konflux Feb 25, 2026
@fgallott
Copy link
Copy Markdown
Author

/jira cherrypick OCPBUGS-78279

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fgallott: Jira Issue OCPBUGS-78279 has been cloned as Jira Issue OCPBUGS-78280. Will retitle bug to link to clone.
/retitle OCPBUGS-78280: [release-4.16] update go mod dependency for konflux

Details

In response to this:

/jira cherrypick OCPBUGS-78279

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 openshift-ci bot changed the title [release-4.16] update go mod dependency for konflux OCPBUGS-78280: [release-4.16] update go mod dependency for konflux Mar 11, 2026
@openshift-ci-robot openshift-ci-robot added 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 Mar 11, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fgallott: This pull request references Jira Issue OCPBUGS-78280, which is invalid:

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

Details

In response to this:

cherry pick of 6f4319a, #240

same as #266

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.

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 16, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ef05e53d-2434-4f91-9b35-7765390d9765

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

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@racheljpg
Copy link
Copy Markdown
Contributor

/approve
/lgtm
/label backport-risk-assessed

@openshift-ci 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 18, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 18, 2026
@sunzhaohua2
Copy link
Copy Markdown

/retest

1 similar comment
@sunzhaohua2
Copy link
Copy Markdown

/retest

@fgallott
Copy link
Copy Markdown
Author

/jira refresh

@openshift-ci-robot 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 24, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fgallott: This pull request references Jira Issue OCPBUGS-78280, 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.16.z) matches configured target version for branch (4.16.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-78279 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-78279 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
  • bug has dependents

Requesting review from QA contact:
/cc @sunzhaohua2

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 openshift-ci bot requested a review from sunzhaohua2 March 24, 2026 05:37
@fgallott
Copy link
Copy Markdown
Author

/retest-required

@fgallott
Copy link
Copy Markdown
Author

/test e2e-gcp-ovn-techpreview

@fgallott
Copy link
Copy Markdown
Author

I think we should override the ci/prow/e2e-gcp-ovn-techpreview since the fix (openshift/installer#8763) was never backported to 4.16.

@damdo
Copy link
Copy Markdown
Member

damdo commented Apr 1, 2026

@fgallott asked about this here: openshift/installer#8763 (comment)

@sunzhaohua2
Copy link
Copy Markdown

/test e2e-gcp-ovn-techpreview

@damdo
Copy link
Copy Markdown
Member

damdo commented Apr 3, 2026

/override ci/prow/e2e-gcp-ovn-techpreview

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 3, 2026

@damdo: Overrode contexts on behalf of damdo: ci/prow/e2e-gcp-ovn-techpreview

Details

In response to this:

/override ci/prow/e2e-gcp-ovn-techpreview

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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 3, 2026

@fgallott: 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-gcp-ovn-techpreview 5318c00 link true /test e2e-gcp-ovn-techpreview

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.

Copy link
Copy Markdown
Member

@damdo damdo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@damdo
Copy link
Copy Markdown
Member

damdo commented Apr 3, 2026

/verified by images job passing

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damdo, racheljpg

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 Apr 3, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 3, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@damdo: This PR has been marked as verified by images job passing.

Details

In response to this:

/verified by images job passing

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-merge-bot openshift-merge-bot bot merged commit 9366599 into openshift:release-4.16 Apr 3, 2026
9 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fgallott: Jira Issue Verification Checks: Jira Issue OCPBUGS-78280
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-78280 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

cherry pick of 6f4319a, #240

same as #266

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

Fix included in accepted release 4.16.0-0.nightly-2026-04-04-074348

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants