fix: 🐛 move release-tools PipelineRuns to .tekton/ root

goern commented

2026-05-25 22:54:18 +00:00

(Migrated from codeberg.org)

Problem

PaC v0.42.0 only scans *.yaml files in the .tekton/ root directory — subdirectories are not scanned. Both release-tools PipelineRun definitions lived in .tekton/release-tools/ and were therefore invisible to PaC. No PipelineRun was ever created for release-tools/v* tag pushes or release-tools PRs.

Diagnosed by: pushing release-tools/v1.0.1 tag, observing PaC controller logs show only 3 root-level PipelineRuns evaluated, release-tools-on-tag-publish never appears.

Also fixed on Codeberg: repo webhook was missing the create event type — tag pushes were never delivered. Added create to the webhook event subscription.

Fix

Move PipelineRun definitions to .tekton/ root with release-tools- prefix:

.tekton/release-tools/on-tag-publish.yaml → .tekton/release-tools-on-tag-publish.yaml
.tekton/release-tools/on-pull-request-build.yaml → .tekton/release-tools-on-pull-request-build.yaml

Task definitions in .tekton/release-tools/tasks/ are unaffected — PaC fetches them by explicit path via pipelinesascode.tekton.dev/task annotation.

Post-merge

After merging: delete and re-push release-tools/v1.0.1 tag to trigger the publish pipeline.

Closes forgejo-mcp-8sz

## Problem PaC v0.42.0 only scans `*.yaml` files in the `.tekton/` root directory — subdirectories are not scanned. Both release-tools PipelineRun definitions lived in `.tekton/release-tools/` and were therefore invisible to PaC. No PipelineRun was ever created for `release-tools/v*` tag pushes or release-tools PRs. Diagnosed by: pushing `release-tools/v1.0.1` tag, observing PaC controller logs show only 3 root-level PipelineRuns evaluated, `release-tools-on-tag-publish` never appears. Also fixed on Codeberg: repo webhook was missing the `create` event type — tag pushes were never delivered. Added `create` to the webhook event subscription. ## Fix Move PipelineRun definitions to `.tekton/` root with `release-tools-` prefix: - `.tekton/release-tools/on-tag-publish.yaml` → `.tekton/release-tools-on-tag-publish.yaml` - `.tekton/release-tools/on-pull-request-build.yaml` → `.tekton/release-tools-on-pull-request-build.yaml` Task definitions in `.tekton/release-tools/tasks/` are unaffected — PaC fetches them by explicit path via `pipelinesascode.tekton.dev/task` annotation. ## Post-merge After merging: delete and re-push `release-tools/v1.0.1` tag to trigger the publish pipeline. Closes forgejo-mcp-8sz

op1st-gitops commented

2026-05-25 22:54:21 +00:00

(Migrated from codeberg.org)

Caution

There are some errors in your PipelineRun template.

PipelineRun	Error
release-tools-on-pull-request-build	`CEL expression evaluation error: expression "event == \"pull_request\" && target_branch == \"main\" &&\nfiles.any.exists(p, p.matches(\"^(image/release-tools/\|\\\\.tekton/release-tools/).*\"))\n" failed to evaluate: no such key: any`

> [!CAUTION] > There are some errors in your PipelineRun template. | PipelineRun | Error | |------|-------| | release-tools-on-pull-request-build | `CEL expression evaluation error: expression "event == \"pull_request\" && target_branch == \"main\" &&\nfiles.any.exists(p, p.matches(\"^(image/release-tools/\|\\\\.tekton/release-tools/).*\"))\n" failed to evaluate: no such key: any` |

op1st-gitops commented

2026-05-25 22:54:22 +00:00

(Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-km6hk is running.

Starting Pipelinerun on-pull-request-km6hk in namespace op1st-pipelines

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n op1st-pipelines on-pull-request-km6hk -f

op1st Pipelines as Code/on-pull-request-km6hk is running. Starting Pipelinerun <b>[on-pull-request-km6hk](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/on-pull-request-km6hk)</b> in namespace <b>op1st-pipelines</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/on-pull-request-km6hk) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n op1st-pipelines on-pull-request-km6hk -f</code>

op1st-gitops commented

2026-05-25 22:54:22 +00:00

(Migrated from codeberg.org)

op1st Pipelines as Code/code-scans- has failed.
There was an error creating the PipelineRun: code-scans-

cannot use the API on the provider platform to create a in_progress status:

op1st Pipelines as Code/code-scans- has <b>failed</b>. There was an error creating the PipelineRun: <b>code-scans-</b> cannot use the API on the provider platform to create a in_progress status:

op1st-gitops commented

2026-05-25 22:55:44 +00:00

(Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-km6hk has successfully validated your commit.

Namespace: op1st-pipelines
PipelineRun: on-pull-request-km6hk

Task Statuses:

Status	Duration	Name
Succeeded	10 seconds	fetch-source
Succeeded	1 minute	build-and-test

op1st Pipelines as Code/on-pull-request-km6hk has <b>successfully</b> validated your commit. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">op1st-pipelines</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/on-pull-request-km6hk">on-pull-request-km6hk</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>10 seconds</td><td> [fetch-source](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/on-pull-request-km6hk/logs/fetch-source) </td></tr> <tr> <td>Succeeded</td> <td>1 minute</td><td> [build-and-test](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/on-pull-request-km6hk/logs/build-and-test) </td></tr> </table>

op1st-gitops commented

2026-05-25 22:57:13 +00:00

(Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-bx2n9 is running.

Starting Pipelinerun on-pull-request-bx2n9 in namespace op1st-pipelines

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n op1st-pipelines on-pull-request-bx2n9 -f

op1st Pipelines as Code/on-pull-request-bx2n9 is running. Starting Pipelinerun <b>[on-pull-request-bx2n9](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/on-pull-request-bx2n9)</b> in namespace <b>op1st-pipelines</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/on-pull-request-bx2n9) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n op1st-pipelines on-pull-request-bx2n9 -f</code>

op1st-gitops commented

2026-05-25 22:57:13 +00:00

(Migrated from codeberg.org)

op1st Pipelines as Code/code-scans-4njjt is running.

Starting Pipelinerun code-scans-4njjt in namespace op1st-pipelines

You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n op1st-pipelines code-scans-4njjt -f

op1st Pipelines as Code/code-scans-4njjt is running. Starting Pipelinerun <b>[code-scans-4njjt](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/code-scans-4njjt)</b> in namespace <b>op1st-pipelines</b> You can monitor the execution using the [op1st Pipelines as Code](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/code-scans-4njjt) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n op1st-pipelines code-scans-4njjt -f</code>

op1st-gitops commented

2026-05-25 22:57:33 +00:00

(Migrated from codeberg.org)

op1st Pipelines as Code/code-scans-4njjt has successfully validated your commit.

Namespace: op1st-pipelines
PipelineRun: code-scans-4njjt

Task Statuses:

Status	Duration	Name
Succeeded	11 seconds	fetch-source
Succeeded	8 seconds	gitleaks-version
Succeeded	9 seconds	gitleaks

op1st Pipelines as Code/code-scans-4njjt has <b>successfully</b> validated your commit. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">op1st-pipelines</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/code-scans-4njjt">code-scans-4njjt</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>11 seconds</td><td> [fetch-source](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/code-scans-4njjt/logs/fetch-source) </td></tr> <tr> <td>Succeeded</td> <td>8 seconds</td><td> [gitleaks-version](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/code-scans-4njjt/logs/gitleaks-version) </td></tr> <tr> <td>Succeeded</td> <td>9 seconds</td><td> [gitleaks](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/code-scans-4njjt/logs/gitleaks) </td></tr> </table>

op1st-gitops commented

2026-05-25 22:58:34 +00:00

(Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-bx2n9 has successfully validated your commit.

Namespace: op1st-pipelines
PipelineRun: on-pull-request-bx2n9

Task Statuses:

Status	Duration	Name
Succeeded	11 seconds	fetch-source
Succeeded	1 minute	build-and-test

op1st Pipelines as Code/on-pull-request-bx2n9 has <b>successfully</b> validated your commit. <ul> <li><b>Namespace</b>: <a href="https://detailurl.setting.custom-console-url-namespace.is.not.configured">op1st-pipelines</a></li> <li><b>PipelineRun:</b> <a href="https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/on-pull-request-bx2n9">on-pull-request-bx2n9</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>11 seconds</td><td> [fetch-source](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/on-pull-request-bx2n9/logs/fetch-source) </td></tr> <tr> <td>Succeeded</td> <td>1 minute</td><td> [build-and-test](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/on-pull-request-bx2n9/logs/build-and-test) </td></tr> </table>

Rows
Columns

fix: 🐛 move release-tools PipelineRuns to .tekton/ root #160

Problem

Fix

Post-merge

Task Statuses:

Task Statuses:

Task Statuses: