release-process

Automate a zero-disaster npm release workflow by enforcing pre-release checks for semver validation, NPM_TOKEN type, and clean git state before version bumping and publication. This prevents mismanaged versions and broken CI pipelines.

Before creating a git tag, validate the semantic version format, verify NPM_TOKEN type integrity, ensure the working branch is clean, and check if the tag already exists. These pre-release checks prevent human error and release disasters.

Handle a broken npm publication by executing structured rollback and fallback procedures provided in the runbook to recover from broken releases and protect production. Post-publish validation steps help detect issues early for rapid rollback.

Yes, this release runbook applies to software teams releasing versioned packages across multiple workspaces. It provides structured end-to-end automation from version bump to GitHub releases and post-mortem steps.

The best way to prevent token issues and mismanaged versions is enforcing explicit guardrails and stepwise automation in CI configuration and release scripts. This includes verifying token type and branch cleanliness before proceeding.

Your release workflow fails because the automation enforces a clean git state as a guardrail to prevent releasing uncommitted or untracked files. Maintaining branch cleanliness is required to ensure a reproducible and zero-disaster release.