Skip to content

chore(deps): update konflux references release-4.18 #761

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Nov 13, 2025
Merged

chore(deps): update konflux references release-4.18 #761

merged 1 commit into from
Nov 13, 2025

Conversation

@red-hat-konflux
Copy link
Contributor

@red-hat-konflux red-hat-konflux bot commented Jun 21, 2025 •
edited
Loading

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 0.4 -> 0.6 ⚠️migration⚠️
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 3ced9a6 -> 33e0361
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 69d578e -> 67b7b22
quay.io/konflux-ci/tekton-catalog/task-prefetch-dependencies-oci-ta 3a1b328 -> 5691652
quay.io/konflux-ci/tekton-catalog/task-push-dockerfile 6124587 -> 74e982c
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 0d22dba -> d5f8a76
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 0.2 -> 0.3 ⚠️migration⚠️
quay.io/konflux-ci/tekton-catalog/task-source-build-oci-ta 0.2 -> 0.3 ⚠️migration⚠️
quay.io/konflux-ci/tekton-catalog/task-summary 870d9a0 -> 3f6e851

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:24
@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.18 branch from c6b305a to ff58ecb Compare June 28, 2025 05:47
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.18 branch 2 times, most recently from edf0234 to df88a83 Compare July 12, 2025 05:18
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.18 branch from df88a83 to d2850b3 Compare July 19, 2025 05:09
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.18 branch 2 times, most recently from a0e156b to 00790e1 Compare August 16, 2025 08:11
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.18 branch from 00790e1 to efc06f9 Compare August 23, 2025 12:13
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.18 branch 2 times, most recently from 99ae39e to 7781f55 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.18 Sep 6, 2025
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.18 branch from 7781f55 to 0378d7a Compare September 13, 2025 08:11
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.18 branch 3 times, most recently from dfe50c7 to da3ccff Compare September 27, 2025 08:12
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.18 branch 2 times, most recently from 93a150f to 66821d1 Compare October 4, 2025 12:10
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.18 branch 2 times, most recently from 02b0da0 to 364259e Compare October 25, 2025 08:13
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/references/release-4.18 branch from 364259e to 978ee63 Compare November 1, 2025 08:21
@red-hat-konflux
chore(deps): update konflux references release-4.18
2d4d8e3 
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.18 branch from 978ee63 to 2d4d8e3 Compare November 8, 2025 12:18
@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

ingvagabund commented Nov 12, 2025

/label backport-risk-assessed

@ingvagabund
Copy link
Member

ingvagabund commented Nov 12, 2025

/verified by CI

@ingvagabund
Copy link
Member

ingvagabund commented Nov 12, 2025

/lgtm

@ingvagabund
Copy link
Member

ingvagabund commented Nov 12, 2025

/approved

@ingvagabund
Copy link
Member

ingvagabund commented Nov 12, 2025

/ok-to-test

@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 Nov 12, 2025
@openshift-ci openshift-ci bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label 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

openshift-ci-robot commented Nov 12, 2025

@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

ingvagabund commented Nov 12, 2025

/approved

@ingvagabund
Copy link
Member

ingvagabund commented Nov 12, 2025

/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

ingvagabund commented Nov 13, 2025

/retest

@ingvagabund
Copy link
Member

ingvagabund commented Nov 13, 2025

PipelineRun "cli-manager-operator-4-18-on-pull-request-qhfpx" failed to finish within "2h0m0s"

@ingvagabund
Copy link
Member

ingvagabund commented Nov 13, 2025

/retest

@ingvagabund ingvagabund merged commit dd1eebe into release-4.18 Nov 13, 2025
3 of 9 checks passed
@ingvagabund ingvagabund deleted the konflux/references/release-4.18 branch November 13, 2025 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ardaguclu ardaguclu Awaiting requested review from ardaguclu

@ingvagabund ingvagabund Awaiting requested review from ingvagabund

Assignees

@ingvagabund ingvagabund

@zhouying7780 zhouying7780

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@ingvagabund @openshift-ci-robot @zhouying7780