Skip to content

chore(deps): update konflux references #609

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
Open
red-hat-konflux wants to merge 1 commit into
base: fbc-4.21
Choose a base branch
from
Open

chore(deps): update konflux references #609

red-hat-konflux wants to merge 1 commit into from
+12 −12

Conversation

@red-hat-konflux
Copy link
Contributor

@red-hat-konflux red-hat-konflux bot commented Jan 10, 2026

This PR contains the following updates:

Package Change
quay.io/konflux-ci/tekton-catalog/task-apply-tags e4017ec -> c89cd10
quay.io/konflux-ci/tekton-catalog/task-build-image-index 39561ac -> 985d1ef
quay.io/konflux-ci/tekton-catalog/task-buildah-remote-oci-ta ef1c062 -> d8b2cd0
quay.io/konflux-ci/tekton-catalog/task-deprecated-image-check 462baed -> 808fe09
quay.io/konflux-ci/tekton-catalog/task-git-clone-oci-ta 0a89e1a -> 56f65a1
quay.io/konflux-ci/tekton-catalog/task-prefetch-dependencies-oci-ta 3e5e834 -> 3620777

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.

@red-hat-konflux
chore(deps): update konflux references
d7c7cbd 
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@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 Jan 10, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 10, 2026

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.

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.

@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 Jan 10, 2026
@ingvagabund
Copy link
Member

ingvagabund commented Jan 10, 2026

/ok-to-test

@ingvagabund
Copy link
Member

ingvagabund commented Jan 10, 2026

/label backport-risk-assessed

@ingvagabund
Copy link
Member

ingvagabund commented Jan 10, 2026

/verified by CI

@ingvagabund
Copy link
Member

ingvagabund commented Jan 10, 2026

/lgtm

@ingvagabund
Copy link
Member

ingvagabund commented Jan 10, 2026

/approve

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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 Jan 10, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 10, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 10, 2026

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

Details

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

openshift-ci bot commented Jan 10, 2026

[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

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

1 similar comment
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 10, 2026

[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

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 Jan 10, 2026
@ingvagabund
Copy link
Member

ingvagabund commented Jan 10, 2026

/retest

4 similar comments
@ingvagabund
Copy link
Member

ingvagabund commented Jan 11, 2026

/retest

@ingvagabund
Copy link
Member

ingvagabund commented Jan 11, 2026

/retest

@ingvagabund
Copy link
Member

ingvagabund commented Jan 11, 2026

/retest

@ingvagabund
Copy link
Member

ingvagabund commented Jan 12, 2026

/retest

@ingvagabund
Copy link
Member

ingvagabund commented Jan 12, 2026

/retest

5 similar comments
@ingvagabund
Copy link
Member

ingvagabund commented Jan 12, 2026

/retest

@ingvagabund
Copy link
Member

ingvagabund commented Jan 13, 2026

/retest

@ingvagabund
Copy link
Member

ingvagabund commented Jan 13, 2026

/retest

@ingvagabund
Copy link
Member

ingvagabund commented Jan 13, 2026

/retest

@ingvagabund
Copy link
Member

ingvagabund commented Jan 14, 2026

/retest

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

@xingxingxia xingxingxia

@wangke19 wangke19

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.

5 participants

@ingvagabund @openshift-ci-robot @zhouying7780 @xingxingxia @wangke19