release-process

Automate a safe npm release workflow by enforcing pre-release checks, semver validation, token verification, and clean git state before proceeding to tag creation and npm publication. This prevents disasters during releases by codifying required hygiene checks.

To publish a GitHub release without breaking CI, enforce CI-state hygiene checks, verify branch cleanliness, and validate semver versions before creating tags. The runbook provides explicit rollback and verification steps to recover if a release fails.

Yes, an Automation NPM token is strictly required for the release process. Verifying this token during pre-release checks ensures npm publication permissions are valid before attempting to publish the package.

Handle a failing npm release by following the built-in rollback and deprecation guidance provided in the runbook. This allows you to quickly recover from failing releases by executing explicit verification and manual fallback steps.

Yes, you can use this release runbook for manual fallback to handle edge cases in CI/CD. It provides comprehensive pre-release validation and manual fallback options to safely execute version bumps, tag creation, and publication manually.

Release workflows fail without a clean git state because uncommitted changes can corrupt tag creation and npm publication. Enforcing a clean git state during pre-release validation prevents disasters and ensures the release runbook executes predictably.