gitea_admin
released this
2026-07-03 22:13:27 +00:00
| 1222 commits to main since this release
Added
- Trunk-name resolver — the staging→trunk branch-rename foundation. Every shared template
that touches the integration trunk now resolves the trunk NAME per-repo at runtime (Forgejo
branches/trunk 200 → trunk, 404 → the legacy staging, anything else → fail loud, never
guess): pipeline-land (PR base), release-cadence + devbump + the three promotes (provenance
clones, ancestry checks, devbump PRs), deploy + deploy-flux (superseded check, ff-main,
rollback), the build/validate family (clone branch + builds/latest gates; git-less publish
pods accept both names), test-ibmi/deploy-ibmi clones, fuzz, and the zerotea crons.
pipectl/shipd resolve project config from raw/branch/trunk with a staging fallback.
Every trunk sensor now watches BOTH refs/heads/staging and refs/heads/trunk (a sensor
deploy and a branch rename can never be atomic — single-ref flips guarantee a dead window),
every CI sensor excludes both, and every project gains a trunk ForgejoBranchProtection
(enablePush:false) that PRE-EXISTS the branch, so a rogue push cannot mint an unprotected
trunk and hijack the resolvers. With no repo renamed yet this release is behavior-neutral;
each repo's rename is now pure branch surgery (create trunk at the staging tip, delete
staging) with zero further sensor/template changes. rpg-hello also gains the trunk
protection its staging never had.
Downloads