release

To coordinate a full npm and GitHub release workflow, you trigger the release process from a chosen source ref to manage canary promotions, enforce verification gates, execute npm publishing, and create the final GitHub release. It handles end-to-end orchestration across multiple systems.

Automating changelog drafting and version calculation involves enforcing preconditions, computing target versions, and generating release artifacts like releases/vYYYY.MDD.P.md. This process ensures stable changelog coordination before executing npm publish gates and GitHub release creation.

A canary smoke test validation gate works by enforcing preconditions during canary promotions before allowing a stable release. It runs verification checks to ensure the canary version passes specific tests, preventing faulty code from advancing to the final npm and GitHub publishing stages.

You can manage Docker and website announcement follow-ups as part of end-to-end release orchestration. The workflow orchestrates multi-system publishing across GitHub, npm, Docker, and the website, coordinating announcement follow-up tasks after the core release artifacts are generated and published.

You need a chosen source ref to trigger the release workflow, but no specific external dependencies are required. The system enforces its own preconditions and computes target versions internally to validate the canary promotion before proceeding to stable npm publishing and GitHub release creation.