• v0.3.4 16c1868ef8

    Release v0.3.4
    All checks were successful
    manifest-check / manifest-vs-tag consistency (pull_request) Successful in 4s
    manifest-check / check (pull_request) Successful in 0s
    Stable

    quartermaster released this 2026-06-25 01:21:01 +02:00 | 1451 commits to main since this release

    The auto-fire of release-draft on prep-PR merge has been retired:
    release-draft is now operator-dispatched only via workflow_dispatch with an explicit tag input. This formalizes the empirical reality — the auto-fire mechanic has never worked since #41 was filed (every release cut to date has used the manual scripts/draft-release.sh fallback) because Forgejo Actions' expression engine cannot reliably resolve github.* / forgejo.* accesses pulling from the pull_request event payload on .closed events. See #41 + #47 for the substrate-evidence (n=3 falsifications during the v0.3.4 sprint's hypothesis-test arc).

    A release-please-shaped redesign (push: branches: [main] trigger + state-file manifest + shell git-log walk — zero pull_request expression-engine exposure) is planned to reinstate single-button auto-fire in the next architectural arc, tracked as #52.

    Fixed

    • .forgejo/workflows/release-draft.yml + docs/integration.md template: drop the pull_request: types: [closed] auto-fire trigger entirely. release-draft is now operator-dispatched only via workflow_dispatch with an explicit tag input. Consumer integration docs updated to match + explain the substrate constraint inline. Closes #41.
    Downloads