Skip to content

Conversation

@red-hat-konflux
Copy link
Contributor

@red-hat-konflux red-hat-konflux bot commented Jun 21, 2025

This PR contains the following updates:

Package Change Notes
quay.io/konflux-ci/tekton-catalog/task-apply-tags 0.1 -> 0.2 ⚠️migration⚠️
quay.io/konflux-ci/tekton-catalog/task-build-image-index 70f2fe8 -> 3411aee
quay.io/konflux-ci/tekton-catalog/task-buildah-remote-oci-ta 0.4 -> 0.6 ⚠️migration⚠️
quay.io/konflux-ci/tekton-catalog/task-clair-scan 0.2 -> 0.3 ⚠️migration⚠️
quay.io/konflux-ci/tekton-catalog/task-clamav-scan 0.2 -> 0.3 ⚠️migration⚠️
quay.io/konflux-ci/tekton-catalog/task-deprecated-image-check eb8136b -> 462baed
quay.io/konflux-ci/tekton-catalog/task-ecosystem-cert-preflight-checks e16e339 -> 9568c51
quay.io/konflux-ci/tekton-catalog/task-git-clone-oci-ta 0761f97 -> 3dc39ea
quay.io/konflux-ci/tekton-catalog/task-init aac8127 -> 3ca52e1
quay.io/konflux-ci/tekton-catalog/task-prefetch-dependencies-oci-ta 3a1b328 -> 5691652
quay.io/konflux-ci/tekton-catalog/task-push-dockerfile-oci-ta c4f87c4 -> 13633d5
quay.io/konflux-ci/tekton-catalog/task-rpms-signature-scan eeaee23 -> 1b6c20a
quay.io/konflux-ci/tekton-catalog/task-sast-snyk-check-oci-ta 89aead3 -> 8ad28b7
quay.io/konflux-ci/tekton-catalog/task-show-sbom 04f15cb -> beb0616
quay.io/konflux-ci/tekton-catalog/task-source-build-oci-ta 0.2 -> 0.3 ⚠️migration⚠️

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: Enabled.

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 ardaguclu and ingvagabund June 21, 2025 06:43
@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 Jun 21, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jun 21, 2025

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

I'm waiting for a openshift 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.

@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.17 branch 2 times, most recently from 77a0949 to e5d46d9 Compare July 5, 2025 05:44
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.17 branch 2 times, most recently from 04f0055 to 341986e Compare July 19, 2025 06:22
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.17 branch 2 times, most recently from 1d790af to 0df6b7e Compare August 16, 2025 08:10
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.17 branch from 0df6b7e to f36041d Compare August 23, 2025 08:11
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.17 branch 2 times, most recently from 7936b6c to 85eced4 Compare September 6, 2025 08:11
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update konflux references chore(deps): update konflux references release-4.17 Sep 6, 2025
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.17 branch from 85eced4 to 7fb52bb Compare September 13, 2025 08:11
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.17 branch 2 times, most recently from b1d6f0d to 3ea2b7c Compare September 27, 2025 08:12
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.17 branch 2 times, most recently from 560c5b6 to 8217737 Compare October 4, 2025 08:15
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.17 branch 2 times, most recently from d0498df to f835612 Compare October 25, 2025 08:12
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.17 branch from f835612 to 7c89917 Compare November 1, 2025 08:16
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/release-4.17 branch from 7c89917 to 5b8d5a7 Compare November 8, 2025 16:11
@ingvagabund ingvagabund added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Nov 12, 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

/approved

@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. labels Nov 12, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 12, 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 removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Nov 12, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 12, 2025
@openshift-ci
Copy link

openshift-ci bot commented Nov 12, 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

/approved

@ingvagabund
Copy link
Member

/approve

@openshift-ci
Copy link

openshift-ci bot commented Nov 12, 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 12, 2025
@ingvagabund ingvagabund added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 12, 2025
@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.

4 participants