Repository navigation
feat: add rollback automation for GitHub releases #17
Description
Quality Gate Reference
- Checklist Item: CCD-008 (Rollback Strategy)
- Current Score: 0.50/1.0
- Impact: Medium — Tier 2 blocker
- Effort: Medium
Description
Rollback workflow exists on feat/autonomous-convergence but is not on main. Implement automatic rollback on release failure:
- Post-release smoke test that validates the published artifact
- On failure, use
author/action-rollbackto delete bad release and tag - Keep previous release installable
For CLI plugins: rollback = delete bad release + ensure previous release remains installable.
Implementation
- Add post-release verification step in release.yml
- Add
author/action-rollbackas conditional step on failure - Merge existing rollback.yml from PR chore: quality improvement 53.9 → 81.5 (tier 2) #1
Acceptance Criteria
- Release pipeline includes post-release verification
- Automatic rollback triggers on verification failure
- CCD-008 score improves
- All existing tests pass
References
- author/action-rollback
- Depends on: CI fixes (issue chore: quality improvement 53.9 → 81.5 (tier 2) #1)
Activity
zircote commentedon Apr 1, 2026
Resolution: Already Implemented on
developThe rollback automation is fully implemented on the
developbranch and will reachmainon next release merge.Evidence
release.yml — Post-release verification + auto-rollback:
verify-releasejob (lines 66–103): validates release exists, is marked latest, and tests pass at the release tagrollback-on-failurejob (lines 104–161): on verification failure, deletes bad release, promotes previous release as latest, and creates a tracking issuerollback.yml — Manual rollback workflow:
workflow_dispatchwith version/reason inputsAcceptance Criteria
main