Repository navigation
release: recover v0.5.0 publication after unreleased changelog preflight stop #281
Description
Objective
Resume the authorized v0.5.0 publication from the immutable existing tag and exact retained release candidate after the release-event preflight stopped before any registry write because CHANGELOG [Unreleased] still contains entries.
Acceptance criteria
- Add an explicit manual recovery dispatch for publish.yaml targeting the existing immutable v0.5.0 tag.
- Preserve the tagged SHA and consume only the successful retained same-SHA 35-artifact candidate from run 30686731253.
- Record and require an explicit maintainer waiver for only the [Unreleased] changelog hygiene check; keep version, tag, checksum, license, npm identity, registry order, and fail-closed publication checks intact.
- Do not rebuild or replace candidate bytes.
- Normal PR CI passes before the recovery dispatch.
- Record the failed no-write publication run 30687300759 and the final recovery run.
Relationships
- Parent/blocker: release: ship GraphForge v0.5.1 with fast-fail recovery #192
- Unblocks publication issues release: create v0.5.1 tag and GitHub Release #194, release: publish graphforge v0.5.1 to PyPI #195, release: publish v0.5.1 Node binding, CLI, and skills #198, and release: publish approved v0.5.1 crates.io surface #196.
Non-goals
- Moving or recreating v0.5.0.
- Running the waived aggregate M1 certification workflows.
- Treating investigate: unexpected checkpoint lock contention in isolated revert test #275 as a publication blocker.
Activity
coderabbitai commentedon Aug 1, 2026
🔗 Related PRs
#268 - fix(release): align artifact records with M1 [merged]
#276 - fix(release): reference M1 publication tracker [open]
#278 - fix(ci): retain certification evidence as artifacts [open]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
DecisionNerd commentedon Aug 1, 2026
Recovery run 30687546572 stopped before registry writes: the candidate-preflight source step calls gh release view but lacked GH_TOKEN. Reopening for the bounded root-cause fix; do not rerun unchanged.