Skip to content

OCPBUGS-77995: [release-4.13] NO-JIRA: update go mod dependency for konflux#1118

Open
fgallott wants to merge 1 commit intoopenshift:release-4.13from
fgallott:hermetic-4.13
Open

OCPBUGS-77995: [release-4.13] NO-JIRA: update go mod dependency for konflux#1118
fgallott wants to merge 1 commit intoopenshift:release-4.13from
fgallott:hermetic-4.13

Conversation

@fgallott
Copy link

cherrypick of 4ecdd01, same as #1117

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 24, 2026
@openshift-ci-robot
Copy link
Contributor

@fgallott: This pull request explicitly references no jira issue.

Details

In response to this:

cherrypick of 4ecdd01, same as #1117

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 review from jhadvig and spadgett February 24, 2026 09:24
@fgallott fgallott changed the title NO-JIRA: update go mod dependency for konflux [release-4.13] NO-JIRA: update go mod dependency for konflux Feb 26, 2026
@fgallott
Copy link
Author

fgallott commented Mar 9, 2026

/jira cherrypick OCPBUGS-77994

@openshift-ci-robot
Copy link
Contributor

@fgallott: Jira Issue OCPBUGS-77994 has been cloned as Jira Issue OCPBUGS-77995. Will retitle bug to link to clone.
/retitle OCPBUGS-77995: [release-4.13] NO-JIRA: update go mod dependency for konflux

Details

In response to this:

/jira cherrypick OCPBUGS-77994

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.13] NO-JIRA: update go mod dependency for konflux OCPBUGS-77995: [release-4.13] NO-JIRA: update go mod dependency for konflux Mar 9, 2026
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 9, 2026
@openshift-ci-robot
Copy link
Contributor

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

  • expected dependent Jira Issue OCPBUGS-77994 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:

cherrypick of 4ecdd01, same as #1117

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.

Copy link
Member

@jhadvig jhadvig left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve
/label backport-risk-assessed
/retest

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

openshift-ci bot commented Mar 11, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fgallott, jhadvig

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 Mar 11, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 11, 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-aws-console 695ddc8 link true /test e2e-aws-console

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.

@yanpzhan
Copy link

Checked in ci jobs, the pr code didn't affect cluster test, there was not block issue.
/verified by yanpzhan

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 13, 2026
@openshift-ci-robot
Copy link
Contributor

@yanpzhan: This PR has been marked as verified by yanpzhan.

Details

In response to this:

Checked in ci jobs, the pr code didn't affect cluster test, there was not block issue.
/verified by yanpzhan

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.

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/invalid-bug Indicates that a referenced Jira bug is invalid 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.

7 participants