docs: Add a release.yml template #13

Merged

ahmad merged 1 commit from feat/release-template into main

2026-08-14 19:50:41 +00:00

ahmad commented

2026-08-14 18:59:11 +00:00

Owner

Issue

Closes #12

Problem

New apps adopt the release flow by cribbing release.yml from an existing repo, so
the canonical shape lives nowhere and drifts between copies.

Solution

Add templates/release.yml — the four-job flow (version → publish → deploy →
notify) wired to release/openbao-fetch/deploy-vps/notify-telegram, with
<PLACEHOLDER>s for the app-specific bits and inline notes (single-image vs matrix,
QEMU for a cross-arch host, deploy-vps vs a local deploy action, humanised vs
commit-list notes). README's "release flow" section points to it.

Review notes

docs:, so it won't bump @v3 — the template is a reference, not consumed. It
parses as valid YAML and passes actionlint bar the expected Forgejo full-URL notes.
Not a runnable workflow (it's under templates/, not .forgejo/workflows/), so
Forgejo never tries to execute it.

Risks and trade-offs

None — additive documentation.

### Issue Closes #12 ### Problem New apps adopt the release flow by cribbing `release.yml` from an existing repo, so the canonical shape lives nowhere and drifts between copies. ### Solution Add `templates/release.yml` — the four-job flow (version → publish → deploy → notify) wired to `release`/`openbao-fetch`/`deploy-vps`/`notify-telegram`, with `<PLACEHOLDER>`s for the app-specific bits and inline notes (single-image vs matrix, QEMU for a cross-arch host, deploy-vps vs a local deploy action, humanised vs commit-list notes). README's "release flow" section points to it. ### Review notes `docs:`, so it won't bump `@v3` — the template is a reference, not consumed. It parses as valid YAML and passes actionlint bar the expected Forgejo full-URL notes. Not a runnable workflow (it's under `templates/`, not `.forgejo/workflows/`), so Forgejo never tries to execute it. ### Risks and trade-offs None — additive documentation.

ahmad added 1 commit

2026-08-14 18:59:11 +00:00

docs: Add a release.yml template a65e71ea79

New apps adopt the release flow by copying release.yml from an existing repo.
Add templates/release.yml — the four-job flow wired to the shared actions with
<PLACEHOLDER>s — and a README pointer, so the canonical shape lives here.

ahmad merged commit 385d5a8201 into main

2026-08-14 19:50:41 +00:00

ahmad deleted branch feat/release-template

2026-08-14 19:50:41 +00:00

ahmad referenced this pull request from a commit

2026-08-14 19:50:42 +00:00

docs: Add a release.yml template (#13)