-
Release v0.4.0
StableAll checks were successfulmanifest-check / manifest-vs-tag consistency (pull_request) Successful in 4smanifest-check / check (pull_request) Successful in 0srelease / decide + act (push) Recovered via manual manifest push at 595c10f (see #78)release / release (push) Recovered via manual manifest push at 595c10f (see #78)released this
2026-06-25 22:19:43 +02:00 | 1423 commits to main since this releaseAdded
Push-triggered rolling-release-PR mechanic — v0.4.0 replaces the v0.3.x operator-dispatched prep flow with a
push: branches: [main]trigger backed by a committed.release-toolkit-manifest.jsonstate file and a shell-based decision engine (scripts/release-decide.sh). On every push to main, the workflow walksgit log <last_released_sha>..HEADand decides one of three modes:noop(no release-relevant content),update(refresh the rolling release-prep PR with the accumulated bump), orcut(the operator merged the rolling PR — firedraft-release.sh+ commit-and-push the manifest update). The substrate-honest escape from the Forgejo Actions expression-engine bug (#41 / #47) that constrained the v0.3.x flow — no${{ github.event.* }}/${{ forgejo.event.* }}accesses on the load-bearing path.Fixed
scripts/release-prep.sh:DRY_RUN_INPUT/DRY_RUN_ENVenv-var sources now use truthy semantics — the literal string"false"no longer falsely enables dry-run (closes #70).scripts/release-prep.sh+.forgejo/workflows/_release.yml: defensive git identity setup beforegit commit— works on fresh CI runner containers without pre-configured git config; configurable viaRELEASE_TOOLKIT_GIT_NAME/RELEASE_TOOLKIT_GIT_EMAILenv vars; consumer-provided config preserved (closes #73).
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads