Skip to content

Conversation

@red-hat-konflux
Copy link
Contributor

@red-hat-konflux red-hat-konflux bot commented Nov 15, 2025

This PR contains the following updates:

Package Change Notes
quay.io/konflux-ci/tekton-catalog/task-apply-tags 4c2b0a2 -> ade0bf9
quay.io/konflux-ci/tekton-catalog/task-build-image-index 3411aee -> 0e90cf8
quay.io/konflux-ci/tekton-catalog/task-buildah-oci-ta 0.6 -> 0.7 ⚠️migration⚠️
quay.io/konflux-ci/tekton-catalog/task-buildah-remote-oci-ta 0.6 -> 0.7 ⚠️migration⚠️
quay.io/konflux-ci/tekton-catalog/task-ecosystem-cert-preflight-checks 9568c51 -> 04f7559
quay.io/konflux-ci/tekton-catalog/task-git-clone-oci-ta 3dc39ea -> ea64f5b
quay.io/konflux-ci/tekton-catalog/task-init 3ca52e1 -> 4072de8
quay.io/konflux-ci/tekton-catalog/task-prefetch-dependencies-oci-ta 5691652 -> 9dbb38e
quay.io/konflux-ci/tekton-catalog/task-push-dockerfile-oci-ta 13633d5 -> 08bba4a
quay.io/konflux-ci/tekton-catalog/task-source-build-oci-ta 282cb5a -> f62ef32

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 added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Nov 15, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 15, 2025

Hi @red-hat-konflux[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.

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.

@ingvagabund ingvagabund added 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. labels Nov 15, 2025
@ingvagabund
Copy link
Member

/ok-to-test

@ingvagabund
Copy link
Member

/label backport-risk-assessed

@ingvagabund
Copy link
Member

/verified by CI

@ingvagabund
Copy link
Member

/lgtm

@ingvagabund
Copy link
Member

/approve

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 15, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 15, 2025
@openshift-ci-robot
Copy link

@ingvagabund: This PR has been marked as verified by CI.

In response to this:

/verified by CI

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 added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 15, 2025
@ingvagabund
Copy link
Member

/retest

7 similar comments
@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

11 similar comments
@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/main branch from 8717d2a to 5f35165 Compare November 22, 2025 09:11
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 22, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 22, 2025

@red-hat-konflux[bot]: 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.

@ingvagabund
Copy link
Member

/lgtm

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

openshift-ci bot commented Nov 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ingvagabund, red-hat-konflux[bot]

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:

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

@ingvagabund
Copy link
Member

/retest

3 similar comments
@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

@ingvagabund
Copy link
Member

/retest

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.

5 participants