release automation never fires: no Forgejo Actions runs (manual tagging in practice) #119

New issue

Closed

opened 2026-06-08 05:59:53 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-08 05:59:53 +00:00

Owner

The Forgejo-canonical release pipeline (.forgejo/workflows/release.yml) is documented as the release mechanism: push to main -> tag-bump cuts the semver tag + Forgejo release. In practice it is not firing.

Evidence:

GET /api/v1/repos/coilyco-flight-deck/cli-guard/actions/tasks returns total_count: 0 - no workflow run has ever executed for this repo.
release.yml was present as of v0.5.0, yet the 6 feat/fix commits between v0.4.0 and that point never produced an auto-tag; v0.5.0 and now v0.6.0 were both cut by hand.

Likely cause: no Forgejo Actions runner registered/online for this repo (or Actions disabled at the repo level). Until it is fixed, every release is a manual git tag -s vX.Y.Z && git push, and the documented "push to main auto-releases" contract in AGENTS.md / docs/release-pipeline.md is misleading.

Fix: register/verify a runner (or enable Actions), then confirm a no-op push cuts a tag. Until then, either make the manual process the documented one or add a guard that fails loudly when no runner picks up the push.

The Forgejo-canonical release pipeline (`.forgejo/workflows/release.yml`) is documented as the release mechanism: push to `main` -> `tag-bump` cuts the semver tag + Forgejo release. In practice it is **not firing**. Evidence: - `GET /api/v1/repos/coilyco-flight-deck/cli-guard/actions/tasks` returns `total_count: 0` - no workflow run has *ever* executed for this repo. - `release.yml` was present as of `v0.5.0`, yet the 6 feat/fix commits between `v0.4.0` and that point never produced an auto-tag; `v0.5.0` and now `v0.6.0` were both cut by hand. Likely cause: no Forgejo Actions runner registered/online for this repo (or Actions disabled at the repo level). Until it is fixed, every release is a manual `git tag -s vX.Y.Z && git push`, and the documented "push to main auto-releases" contract in AGENTS.md / docs/release-pipeline.md is misleading. Fix: register/verify a runner (or enable Actions), then confirm a no-op push cuts a tag. Until then, either make the manual process the documented one or add a guard that fails loudly when no runner picks up the push.

coilysiren referenced this issue

2026-06-10 17:34:57 +00:00

godoc-current.txt is GOOS-dependent (sandbox per-OS docs); cross-platform commits trip the hook #126

coilysiren

2026-06-17 07:04:51 +00:00