chore(ci): soft-disable Forgejo release workflow auto-trigger #151

Merged

goern merged 0 commits from refs/pull/151/head into main

2026-05-25 11:31:02 +00:00

goern commented

2026-05-25 11:30:08 +00:00

(Migrated from codeberg.org)

Summary

Switches .forgejo/workflows/release.yml trigger from push: tags: ['v*'] to workflow_dispatch only. After this PR, the op1st Tekton release pipeline (added in #150) is the sole auto-firing release path on tag push.

The workflow file stays in tree as a manual fallback. Re-enable on demand via Codeberg UI → Actions → Run workflow, or revert this commit.

Tracks bead forgejo-mcp-n85. Full removal of .forgejo/workflows/release.yml is deferred to forgejo-mcp-gdz after two consecutive successful Tekton releases satisfy the ADR cutover criteria.

Why soft-disable instead of delete

Zero real Tekton releases have run yet. Deleting now means the next v* tag's first real Tekton execution has no fallback if the PaC trigger or token scope is wrong. workflow_dispatch keeps all secrets and config intact and reduces "disable" to a one-line revert.

ADR

docs/design/release-pipeline-migration.md updated:

Status: Proposed (parallel-run phase) → Accepted (soft-cutover phase)
Status-history table added so future readers see the migration phases.

Test plan

Push next v* tag (e.g. v2.24.0 when due). Confirm Codeberg Actions shows no release workflow run for the tag.
Confirm the Tekton on-tag-push-release PipelineRun in op1st-pipelines namespace fires and produces all 8 expected release assets.
If Tekton fails: re-trigger Forgejo workflow via Codeberg UI (Actions → release → Run workflow → tag v2.24.0). Confirm it produces the same assets it did pre-soft-disable.
After two successful Tekton releases, open follow-up PR per forgejo-mcp-gdz removing .forgejo/workflows/release.yml entirely.

## Summary Switches `.forgejo/workflows/release.yml` trigger from `push: tags: ['v*']` to `workflow_dispatch` only. After this PR, the op1st Tekton release pipeline (added in #150) is the sole auto-firing release path on tag push. The workflow file **stays in tree** as a manual fallback. Re-enable on demand via Codeberg UI → Actions → Run workflow, or revert this commit. Tracks bead `forgejo-mcp-n85`. Full removal of `.forgejo/workflows/release.yml` is deferred to `forgejo-mcp-gdz` after two consecutive successful Tekton releases satisfy the ADR cutover criteria. ## Why soft-disable instead of delete Zero real Tekton releases have run yet. Deleting now means the next `v*` tag's first real Tekton execution has no fallback if the PaC trigger or token scope is wrong. `workflow_dispatch` keeps all secrets and config intact and reduces "disable" to a one-line revert. ## ADR `docs/design/release-pipeline-migration.md` updated: - Status: `Proposed (parallel-run phase)` → `Accepted (soft-cutover phase)` - Status-history table added so future readers see the migration phases. ## Test plan - [ ] Push next `v*` tag (e.g. `v2.24.0` when due). Confirm Codeberg Actions shows **no** `release` workflow run for the tag. - [ ] Confirm the Tekton `on-tag-push-release` PipelineRun in `op1st-pipelines` namespace fires and produces all 8 expected release assets. - [ ] If Tekton fails: re-trigger Forgejo workflow via Codeberg UI (Actions → release → Run workflow → tag `v2.24.0`). Confirm it produces the same assets it did pre-soft-disable. - [ ] After two successful Tekton releases, open follow-up PR per `forgejo-mcp-gdz` removing `.forgejo/workflows/release.yml` entirely.

op1st-gitops commented

2026-05-25 11:30:20 +00:00

(Migrated from codeberg.org)

op1st Pipelines as Code/code-scans-dm5k9 is running.

Starting Pipelinerun code-scans-dm5k9 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-dm5k9 -f

op1st Pipelines as Code/code-scans-dm5k9 is running. Starting Pipelinerun <b>[code-scans-dm5k9](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/code-scans-dm5k9)</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-dm5k9) 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-dm5k9 -f</code>

op1st-gitops commented

2026-05-25 11:30:20 +00:00

(Migrated from codeberg.org)

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

Starting Pipelinerun on-pull-request-dxpsf 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-dxpsf -f

op1st Pipelines as Code/on-pull-request-dxpsf is running. Starting Pipelinerun <b>[on-pull-request-dxpsf](https://console-openshift-console.apps.nostromo.erdgeschoss.b4mad.emea.operate-first.cloud/k8s/ns/op1st-pipelines/tekton.dev~v1~PipelineRun/on-pull-request-dxpsf)</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-dxpsf) 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-dxpsf -f</code>

op1st-gitops commented

2026-05-25 11:30:45 +00:00

(Migrated from codeberg.org)

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

Namespace: op1st-pipelines
PipelineRun: code-scans-dm5k9

Task Statuses:

Status	Duration	Name
Succeeded	14 seconds	fetch-source
Succeeded	9 seconds	gitleaks-version
Succeeded	10 seconds	gitleaks

op1st Pipelines as Code/code-scans-dm5k9 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-dm5k9">code-scans-dm5k9</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>14 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-dm5k9/logs/fetch-source) </td></tr> <tr> <td>Succeeded</td> <td>9 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-dm5k9/logs/gitleaks-version) </td></tr> <tr> <td>Succeeded</td> <td>10 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-dm5k9/logs/gitleaks) </td></tr> </table>

op1st-gitops commented

2026-05-25 11:31:07 +00:00

(Migrated from codeberg.org)

op1st Pipelines as Code/on-pull-request-dxpsf

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

Task Statuses:

Status	Duration	Name
Succeeded	14 seconds	fetch-source
Failed	32 seconds	build-and-test

Failure snippet:

task build-and-test has the status "TaskRunCancelled":

TaskRun "on-pull-request-dxpsf-build-and-test" was cancelled. TaskRun cancelled as the PipelineRun it belongs to has been cancelled.

op1st Pipelines as Code/on-pull-request-dxpsf <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-dxpsf">on-pull-request-dxpsf</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>14 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-dxpsf/logs/fetch-source) </td></tr> <tr> <td>Failed</td> <td>32 seconds</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-dxpsf/logs/build-and-test) </td></tr> </table> <hr> <h4>Failure snippet:</h4> task <b>build-and-test</b> has the status <b>"TaskRunCancelled"</b>: <pre>TaskRun "on-pull-request-dxpsf-build-and-test" was cancelled. TaskRun cancelled as the PipelineRun it belongs to has been cancelled.</pre>