Skip to content

Catalog update [tekton-fbc-operator-2026-418] [v4.18,v4.19,v4.20,v4.21]#6772

Open
rh-operator-bundle-bot wants to merge 1 commit intostagefrom
add-tekton-fbc-operator-2026-418-0.0.24-to-fbc-10705
Open

Catalog update [tekton-fbc-operator-2026-418] [v4.18,v4.19,v4.20,v4.21]#6772
rh-operator-bundle-bot wants to merge 1 commit intostagefrom
add-tekton-fbc-operator-2026-418-0.0.24-to-fbc-10705

Conversation

@rh-operator-bundle-bot
Copy link
Copy Markdown
Collaborator

🚀 Automated PR: FBC Release Process

This pull request was automatically generated as part of the FBC release process.

  • Operator: tekton-fbc-operator-2026-418
  • Version: 0.0.24
  • Image: registry.connect.stage.redhat.com/tekton-pipeline-automation/tekton-fbc-operator-2026-418@sha256:957df821e02b3bf3af903b8e6ea54534fa4c0ac6c3778eecbe66508849a699c1

For reference, see the previous PR.

If you have any questions or need modifications, please let us know!

Signed-off-by: rh-operator-bundle-bot <exd-guild-isv+operators@redhat.com>
@rh-operator-bundle-bot rh-operator-bundle-bot added operator-hosted-pipeline/started approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 17, 2026
@rh-operator-bundle-bot rh-operator-bundle-bot changed the title Auto FBC release tekton-fbc-operator-2026-418 0.0.24 Catalog update [tekton-fbc-operator-2026-418] [v4.18,v4.19,v4.20,v4.21] Feb 17, 2026
@rh-operator-bundle-bot
Copy link
Copy Markdown
Collaborator Author

@rh-operator-bundle-bot
Copy link
Copy Markdown
Collaborator Author

There were some errors while publishing your Operator Bundle. You can use this support case to contact the Red Hat certification team for review.

@rh-operator-bundle-bot
Copy link
Copy Markdown
Collaborator Author

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-runcvjzg
Start Time: 2026-02-17 04:47:47+00:00

Tasks

Status Task Start Time Duration
✔️ get-pr-number 2026-02-17 04:47:53+00:00 4 seconds
✔️ acquire-lease 2026-02-17 04:48:02+00:00 5 seconds
✔️ set-github-started-label 2026-02-17 04:48:15+00:00 7 seconds
✔️ set-github-status-pending 2026-02-17 04:48:16+00:00 7 seconds
✔️ set-env 2026-02-17 04:48:27+00:00 6 seconds
✔️ clone-repository 2026-02-17 04:48:38+00:00 25 seconds
✔️ clone-repository-base 2026-02-17 04:48:39+00:00 24 seconds
✔️ detect-changes 2026-02-17 04:49:04+00:00 42 seconds
✔️ check-permissions 2026-02-17 04:49:49+00:00 41 seconds
✔️ set-github-pr-title 2026-02-17 04:50:32+00:00 7 seconds
✔️ read-config 2026-02-17 04:50:42+00:00 36 seconds
✔️ resolve-pr-type 2026-02-17 04:51:21+00:00 4 seconds
✔️ validate-catalog-format 2026-02-17 04:51:28+00:00 45 seconds
✔️ build-fragment-images 2026-02-17 04:52:14+00:00 58 seconds
✔️ content-hash 2026-02-17 04:53:13+00:00 35 seconds
✔️ certification-project-check 2026-02-17 04:53:52+00:00 39 seconds
✔️ get-organization 2026-02-17 04:54:34+00:00 37 seconds
✔️ get-pyxis-certification-data 2026-02-17 04:55:14+00:00 40 seconds
✔️ verify-project 2026-02-17 04:55:56+00:00 6 seconds
✔️ update-cert-project-status 2026-02-17 04:56:05+00:00 5 seconds
✔️ static-tests 2026-02-17 04:56:13+00:00 48 seconds
✔️ merge-registry-credentials 2026-02-17 04:57:02+00:00 14 seconds
✔️ digest-pinning 2026-02-17 04:57:20+00:00 41 seconds
verify-pinned-digest 2026-02-17 04:58:03+00:00 2 seconds

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/3c6833097c221a588da7aa78ca1604e8

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 19, 2026
@openshift-merge-robot
Copy link
Copy Markdown

PR needs rebase.

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.

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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. operator-hosted-pipeline/failed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants