release: port pipeline from github Actions to forgejo Actions #80

New issue

Closed

opened 2026-05-25 06:40:59 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-05-25 06:40:59 +00:00

Owner

Problem

The release pipeline at .github/workflows/release.yml is github-coupled and won't work now that forgejo is canonical. It uses mathieudutour/github-tag-action, softprops/action-gh-release, and gh api against github's Contents API. Forgejo runners can't authenticate to github write APIs and the third-party marketplace actions are github-API-only. The brew Formula already points at forgejo URLs (closed by #79), so the pipeline needs to actually run on forgejo to keep the Formula in sync with new releases.

Change

.forgejo/workflows/release.yml: forgejo-canonical pipeline. Triggers on push to forgejo main. Uses the three shared composite actions in coilysiren/agentic-os/actions/ (tag-bump, create-release, bump-formula) which speak forgejo APIs only. Auto-issued ${{ github.token }} (forgejo's compatibility name) handles same-repo writes.
.github/workflows/release.yml: deleted. Github becomes read-only mirror; releases are cut on forgejo only.
AGENTS.md "Release framework" section: rewritten to describe the forgejo flow + name the shared composite actions. "Post-push follow-up" CI-verify step updated to point at forgejo's Actions UI / API.

Not migrated in this change

Windows .exe cross-build + coilysiren/scoop-bucket autoupdate. Blocked on migrating scoop-bucket to forgejo (separate sweep). Until that lands, Windows users get nothing from a forgejo-only release and need make install-windows.

Push flow

Forgejo is canonical, so git push should target forgejo. The github remote stays as origin for historical reasons but won't receive automated commits anymore. Eventually coily repo on github will be archived (separate decision).

**Problem** The release pipeline at `.github/workflows/release.yml` is github-coupled and won't work now that forgejo is canonical. It uses `mathieudutour/github-tag-action`, `softprops/action-gh-release`, and `gh api` against github's Contents API. Forgejo runners can't authenticate to github write APIs and the third-party marketplace actions are github-API-only. The brew Formula already points at forgejo URLs (closed by #79), so the pipeline needs to actually run on forgejo to keep the Formula in sync with new releases. **Change** - `.forgejo/workflows/release.yml`: forgejo-canonical pipeline. Triggers on push to forgejo main. Uses the three shared composite actions in `coilysiren/agentic-os/actions/` (tag-bump, create-release, bump-formula) which speak forgejo APIs only. Auto-issued `${{ github.token }}` (forgejo's compatibility name) handles same-repo writes. - `.github/workflows/release.yml`: deleted. Github becomes read-only mirror; releases are cut on forgejo only. - `AGENTS.md` "Release framework" section: rewritten to describe the forgejo flow + name the shared composite actions. "Post-push follow-up" CI-verify step updated to point at forgejo's Actions UI / API. **Not migrated in this change** - Windows `.exe` cross-build + `coilysiren/scoop-bucket` autoupdate. Blocked on migrating scoop-bucket to forgejo (separate sweep). Until that lands, Windows users get nothing from a forgejo-only release and need `make install-windows`. **Push flow** Forgejo is canonical, so `git push` should target forgejo. The github remote stays as `origin` for historical reasons but won't receive automated commits anymore. Eventually `coily` repo on github will be archived (separate decision).

coilysiren referenced this issue from a commit

2026-05-25 06:41:28 +00:00

release: port pipeline from github Actions to forgejo Actions

coilysiren closed this issue

2026-05-25 06:41:28 +00:00

coilysiren referenced this issue from a commit

2026-05-25 06:49:58 +00:00

ci(release): trigger forgejo release after jq self-install fix

coilysiren referenced this issue

2026-05-25 06:57:36 +00:00

scoop: migrate Windows .exe + scoop-bucket pipeline to forgejo #82

coilysiren referenced this issue from a commit