Skip to content

Conversation

@red-hat-konflux-kflux-prd-rh02
Copy link
Contributor

@red-hat-konflux-kflux-prd-rh02 red-hat-konflux-kflux-prd-rh02 bot commented Dec 6, 2025

This PR contains the following updates:

Package Change
quay.io/konflux-ci/tekton-catalog/task-apply-tags a61d8a6 -> e4017ec
quay.io/konflux-ci/tekton-catalog/task-build-image-index 803ae1e -> 39561ac
quay.io/konflux-ci/tekton-catalog/task-buildah-remote-oci-ta ee5e01e -> ef1c062
quay.io/konflux-ci/tekton-catalog/task-clair-scan 8ec7d7b -> ee558db
quay.io/konflux-ci/tekton-catalog/task-git-clone-oci-ta ea64f5b -> 0a89e1a
quay.io/konflux-ci/tekton-catalog/task-init 4072de8 -> 75b88ee

Configuration

📅 Schedule: Branch creation - Between 05:00 AM and 11:59 PM, only on Saturday ( * 5-23 * * 6 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

@openshift-ci openshift-ci bot requested review from andfasano and rwsu December 6, 2025 08:13
@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Dec 6, 2025
@openshift-ci
Copy link

openshift-ci bot commented Dec 6, 2025

Hi @red-hat-konflux-kflux-prd-rh02[bot]. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

Signed-off-by: red-hat-konflux-kflux-prd-rh02 <190377777+red-hat-konflux-kflux-prd-rh02[bot]@users.noreply.github.com>
@red-hat-konflux-kflux-prd-rh02 red-hat-konflux-kflux-prd-rh02 bot force-pushed the konflux/references/release-4.20 branch from 32fbee8 to 98ceb8b Compare December 13, 2025 08:08
@bfournie
Copy link
Contributor

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 18, 2025
@bfournie
Copy link
Contributor

/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 Dec 18, 2025
@bfournie
Copy link
Contributor

/approve

@openshift-ci
Copy link

openshift-ci bot commented Dec 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bfournie, red-hat-konflux-kflux-prd-rh02[bot]

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 Dec 18, 2025
@bfournie
Copy link
Contributor

/retitle OCPBUGS-69830: Update Konflux references

@openshift-ci openshift-ci bot changed the title Update Konflux references OCPBUGS-69830: Update Konflux references Dec 18, 2025
@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 Dec 18, 2025
@openshift-ci-robot
Copy link

@red-hat-konflux-kflux-prd-rh02[bot]: This pull request references Jira Issue OCPBUGS-69830, which is invalid:

  • expected Jira Issue OCPBUGS-69830 to depend on a bug targeting a version in 4.21.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.

Details

In response to this:

This PR contains the following updates:

Package Change
quay.io/konflux-ci/tekton-catalog/task-apply-tags a61d8a6 -> e4017ec
quay.io/konflux-ci/tekton-catalog/task-build-image-index 803ae1e -> 39561ac
quay.io/konflux-ci/tekton-catalog/task-buildah-remote-oci-ta ee5e01e -> ef1c062
quay.io/konflux-ci/tekton-catalog/task-clair-scan 8ec7d7b -> ee558db
quay.io/konflux-ci/tekton-catalog/task-git-clone-oci-ta ea64f5b -> 0a89e1a
quay.io/konflux-ci/tekton-catalog/task-init 4072de8 -> 75b88ee

Configuration

📅 Schedule: Branch creation - Between 05:00 AM and 11:59 PM, only on Saturday ( * 5-23 * * 6 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

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.

@bfournie
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 18, 2025
@bfournie
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link

@bfournie: This pull request references Jira Issue OCPBUGS-69830, 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.

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.

@bfournie
Copy link
Contributor

/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 Dec 18, 2025
@openshift-ci-robot
Copy link

@bfournie: This pull request references Jira Issue OCPBUGS-69830, 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.20.z) matches configured target version for branch (4.20.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-69829 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-69829 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
  • bug has dependents

Requesting review from QA contact:
/cc @mhanss

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 mhanss December 18, 2025 14:48
@openshift-ci
Copy link

openshift-ci bot commented Dec 18, 2025

@red-hat-konflux-kflux-prd-rh02[bot]: all tests passed!

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.

@bfournie
Copy link
Contributor

/verified by 'Red Hat Konflux / ove-ui-4-20-enterprise-contract / ove-ui-iso-4-20'

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 18, 2025
@openshift-ci-robot
Copy link

@bfournie: This PR has been marked as verified by 'Red Hat Konflux / ove-ui-4-20-enterprise-contract / ove-ui-iso-4-20'.

Details

In response to this:

/verified by 'Red Hat Konflux / ove-ui-4-20-enterprise-contract / ove-ui-iso-4-20'

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 8cdae12 into release-4.20 Dec 18, 2025
12 checks passed
@openshift-ci-robot
Copy link

@red-hat-konflux-kflux-prd-rh02[bot]: Jira Issue Verification Checks: Jira Issue OCPBUGS-69830
✔️ 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-69830 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:

This PR contains the following updates:

Package Change
quay.io/konflux-ci/tekton-catalog/task-apply-tags a61d8a6 -> e4017ec
quay.io/konflux-ci/tekton-catalog/task-build-image-index 803ae1e -> 39561ac
quay.io/konflux-ci/tekton-catalog/task-buildah-remote-oci-ta ee5e01e -> ef1c062
quay.io/konflux-ci/tekton-catalog/task-clair-scan 8ec7d7b -> ee558db
quay.io/konflux-ci/tekton-catalog/task-git-clone-oci-ta ea64f5b -> 0a89e1a
quay.io/konflux-ci/tekton-catalog/task-init 4072de8 -> 75b88ee

Configuration

📅 Schedule: Branch creation - Between 05:00 AM and 11:59 PM, only on Saturday ( * 5-23 * * 6 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

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
Contributor

Fix included in accepted release 4.20.0-0.nightly-2025-12-19-223244

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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants