Merging a release-labeled PR should BE the release — auto-tag + publish on merge (box#96 twin) #47
Labels
No labels
attention
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-ruling
needs-triage
offsite
post-merge
ready
release
scope:bootstrap
scope:coolify
scope:db
scope:docs
scope:drill
scope:installer
scope:labels
scope:platform
scope:runner
scope:users
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: heavy-duty/rig#47
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
rig twin of heavy-duty/box#96 — full design and rationale there.
Summary: the agent's ceremony PR carries the
releaselabel and the bumpedVERSION; the maintainer's merge is the ship decision. Apull_request: closedworkflow (merged + labeled) asserts, fail-loud: non--devversion → version changed in this PR (the-devinterlock) → changelog top section matches and extracts viarelease-lib.sh→ no existing tag/release. Then, same job: API-tag the merge commit + publish with the extracted notes. Existing tag-push path stays as manual fallback.rig specifics: version in the
VERSIONfile; no assets (source tarball is the package);changelog_sectionfrom.github/scripts/release-lib.shis the extractor to reuse.🤖 From the release-ceremony retro with the operator.