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

New issue

Closed

opened 2026-06-04 12:02:32 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-04 12:02:32 +00:00

Owner

Problem

ward's release pipeline lives in .github/workflows/release.yml and builds on GitHub Actions. Canonical history is Forgejo, and the rest of the fleet (coily, otel-a2a-relay-cli, repo-recall) already releases from .forgejo/workflows. ward is the laggard: merging to Forgejo main does not release, because the build only fires on a GitHub main push - which requires a direct push to the PR-gated GitHub mirror.

Change

Move the release off GitHub Actions onto Forgejo Actions, matching the o2r-cli / coily pattern:

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

Assumptions (flag if wrong)

Forgejo secrets FORGEJO_TOKEN (tap + repo write) and GITHUB_MIRROR_PAT (mirror push) exist for ward, as they do for coily/o2r-cli.
Forgejo runner label docker is registered.
Forgejo has the v0.5.x tags (verified: it does, up to v0.5.8), so tag-bump computes v0.6.0 from the pending feat: ward pkg brew.

First run on merge releases v0.6.0 (pkg brew + this migration).

## Problem ward's release pipeline lives in `.github/workflows/release.yml` and builds on GitHub Actions. Canonical history is Forgejo, and the rest of the fleet (coily, otel-a2a-relay-cli, repo-recall) already releases from `.forgejo/workflows`. ward is the laggard: merging to Forgejo `main` does not release, because the build only fires on a GitHub `main` push - which requires a direct push to the PR-gated GitHub mirror. ## Change Move the release off GitHub Actions onto Forgejo Actions, matching the o2r-cli / coily pattern: - `.forgejo/workflows/release.yml` - `runs-on: docker`, `tag-bump` + `create-release` (shared `coilysiren/agentic-os/actions/*`), then `bump-tap-formula` (central flight-deck tap) + `bump-formula` (in-repo fallback) via the Forgejo Contents API, skip-CI marked. ward builds from source, so no prebuilt-asset matrix (unlike o2r). - `.forgejo/workflows/mirror-to-github.yml` - force-push main + tags to the read-only GitHub mirror (coily pattern). - Remove `.github/workflows/release.yml`. `test.yml` stays on GitHub for now. - AGENTS release section updated. ## Assumptions (flag if wrong) - Forgejo secrets `FORGEJO_TOKEN` (tap + repo write) and `GITHUB_MIRROR_PAT` (mirror push) exist for ward, as they do for coily/o2r-cli. - Forgejo runner label `docker` is registered. - Forgejo has the `v0.5.x` tags (verified: it does, up to v0.5.8), so tag-bump computes v0.6.0 from the pending `feat: ward pkg brew`. First run on merge releases v0.6.0 (pkg brew + this migration).

coilysiren referenced this issue from a commit

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

feat: migrate ward release to Forgejo Actions

coilysiren referenced this issue from a pull request that will close it,

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

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

coilysiren closed this issue

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