release

To automate a full software deployment for Paperclip, this Skill coordinates changelog generation, verification, Docker smoke testing, GitHub Release creation, and post-release follow-up tasks in a single workflow. It manages both canary and stable releases with minimal manual intervention.

End-to-end release management here includes preconditions checking, release version determination, changelog updating, candidate verification, and Docker smoke testing. It orchestrates the complete release pipeline from initial checks to GitHub Release creation and post-release tasks.

You can automatically generate changelogs and create a GitHub Release by triggering this Skill's release coordination workflow. It drafts the changelog, verifies the release candidate, runs Docker smoke tests, and then publishes the final GitHub Release.

Yes, this release automation workflow supports both canary and stable version management. It automates canary releases directly from the master branch and handles manual stable promotions from chosen commits to ensure version control flexibility.

Yes, Docker is required for running smoke testing during the software deployment process. The Skill explicitly performs Docker smoke testing as a verification step before creating the final GitHub Release to ensure deployment stability.

The main limitation is that this release management automation is specifically tailored for the Paperclip context. It requires passing preconditions checking and verification steps, meaning any failures in changelog updating or Docker smoke testing will halt the deployment process.