release

Release orchestration automates end-to-end publication by coordinating verification, testing, changelog generation, and GitHub releases. It enforces preconditions like a clean working tree and CI gate, then orchestrates steps from tag creation to release publishing.

Canary-driven validation for stable promotion is a process that validates canary builds before moving them to stable. This skill coordinates canary validation and promotes validated builds to stable status after passing smoke tests.

To generate changelogs and run smoke tests during a release, this skill coordinates stable changelog notes and orchestrates Docker-onboard-smoke tests. It manages these tasks sequentially as part of the end-to-end release workflow.

Release orchestration enforces specific preconditions before starting: a clean working tree, a candidate SHA, and a passing CI gate. These checks ensure the repository is in a valid state before changelog generation and tag creation begin.

Automated release orchestration does not work without a clean working tree. A clean working tree, candidate SHA, and CI gate are mandatory preconditions enforced before proceeding with any release or publication steps.

The best way to coordinate end-to-end Paperclip releases is using an orchestration skill that automates the full workflow. It manages canary validation, smoke testing, changelog drafting, and GitHub release publication to reduce manual toil and risk.