feat: migrate ward release to Forgejo Actions (build from Forgejo, not GitHub) #55

Merged

coilysiren merged 1 commit from feat/forgejo-release into main

2026-06-04 12:05:23 +00:00

coilysiren commented

2026-06-04 12:04:54 +00:00

Owner

What

Moves ward's release pipeline off GitHub Actions onto Forgejo Actions, so the build runs on the canonical host. ward was the last fleet CLI still releasing from .github/workflows — coily, otel-a2a-relay-cli, and repo-recall already build from .forgejo/workflows.

Why

release.yml lived on GitHub and fired only on a GitHub main push. With Forgejo canonical and the GitHub mirror PR-gated, merging to Forgejo main did not release — there was no path to trigger the build without a direct push to the gated GitHub mirror. Building from Forgejo fixes that: merge to Forgejo main → release.

Changes

.forgejo/workflows/release.yml — runs-on: docker; tag-bump + create-release (shared coilysiren/agentic-os/actions/*), then bump-tap-formula (central flight-deck tap) and bump-formula (in-repo fallback) via the Forgejo Contents API, skip-CI marked. ward builds from source, so no prebuilt-asset matrix (unlike o2r-cli).
.forgejo/workflows/mirror-to-github.yml — force-push main + tags to the read-only GitHub mirror (coily pattern; no-ops without GITHUB_MIRROR_PAT).
Removed .github/workflows/release.yml. test.yml stays on GitHub for now.
AGENTS release section updated.

First-run effect

Merging this to Forgejo main fires the new pipeline and cuts v0.6.0 (feat: since v0.5.8 → minor), which also includes the already-merged ward pkg brew (#53). Then brew upgrade ward and the o2r-ansible-debug board repo's ward pkg brew bundle deps path goes live.

Assumptions to confirm

Forgejo secrets FORGEJO_TOKEN (tap + repo contents write) and GITHUB_MIRROR_PAT (mirror push) exist for ward, as for coily/o2r-cli.
Forgejo runner label docker is registered.
Forgejo has the v0.5.x tags — verified, up to v0.5.8.

closes #54

## What Moves ward's release pipeline off GitHub Actions onto **Forgejo Actions**, so the build runs on the canonical host. ward was the last fleet CLI still releasing from `.github/workflows` — coily, otel-a2a-relay-cli, and repo-recall already build from `.forgejo/workflows`. ## Why `release.yml` lived on GitHub and fired only on a GitHub `main` push. With Forgejo canonical and the GitHub mirror PR-gated, merging to Forgejo `main` did **not** release — there was no path to trigger the build without a direct push to the gated GitHub mirror. Building from Forgejo fixes that: merge to Forgejo `main` → release. ## Changes - **`.forgejo/workflows/release.yml`** — `runs-on: docker`; `tag-bump` + `create-release` (shared `coilysiren/agentic-os/actions/*`), then `bump-tap-formula` (central flight-deck tap) and `bump-formula` (in-repo fallback) via the Forgejo Contents API, skip-CI marked. ward builds from source, so no prebuilt-asset matrix (unlike o2r-cli). - **`.forgejo/workflows/mirror-to-github.yml`** — force-push main + tags to the read-only GitHub mirror (coily pattern; no-ops without `GITHUB_MIRROR_PAT`). - **Removed `.github/workflows/release.yml`.** `test.yml` stays on GitHub for now. - **AGENTS** release section updated. ## First-run effect Merging this to Forgejo `main` fires the new pipeline and cuts **v0.6.0** (`feat:` since v0.5.8 → minor), which also includes the already-merged `ward pkg brew` (#53). Then `brew upgrade ward` and the o2r-ansible-debug board repo's `ward pkg brew bundle` deps path goes live. ## Assumptions to confirm - Forgejo secrets `FORGEJO_TOKEN` (tap + repo contents write) and `GITHUB_MIRROR_PAT` (mirror push) exist for ward, as for coily/o2r-cli. - Forgejo runner label `docker` is registered. - Forgejo has the `v0.5.x` tags — **verified**, up to v0.5.8. closes #54

coilysiren added 1 commit

2026-06-04 12:04:54 +00:00

feat: migrate ward release to Forgejo Actions 62e2119701

Move the release pipeline off .github/workflows onto .forgejo/workflows so
the build runs on Forgejo (canonical), matching coily/o2r-cli/repo-recall:

- .forgejo/workflows/release.yml: tag-bump + create-release (shared
  agentic-os actions, runs-on docker), then bump-tap-formula + bump-formula
  via the Forgejo Contents API (skip-CI marked). Build-from-source, no asset
  matrix.
- .forgejo/workflows/mirror-to-github.yml: force-push main + tags to the
  read-only GitHub mirror.
- Remove .github/workflows/release.yml; test.yml stays on GitHub.
- AGENTS release section updated.

Merging this to Forgejo main fires the first Forgejo release (v0.6.0,
including ward pkg brew).

closes #54

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

coilysiren merged commit eb9a08d665 into main

2026-06-04 12:05:23 +00:00

coilysiren referenced this pull request from a commit

2026-06-04 12:05:25 +00:00

Merge pull request 'feat: migrate ward release to Forgejo Actions (build from Forgejo, not GitHub)' (#55) from feat/forgejo-release into main

coilysiren referenced this pull request

2026-06-06 21:57:13 +00:00

ci: run tap bump on the dedicated tap-writer runner #61

coilysiren referenced this pull request

2026-06-06 21:58:07 +00:00

ci: run tap bump on the dedicated tap-writer runner #47

coilysiren referenced this pull request