What problem does it solve?
It prevents CI/CD and release workflows from failing in costly ways due to invalid semver tags, incorrect npm token types, missing propagation retries, and accidental draft-release behavior.
Core Features & Use Cases
- Semver Validation Gate: Enforces npm-compatible 3-part semver (and prerelease formats) before publish, rejecting invalid 4-part versions.
- NPM Token Type Verification: Ensures NPM_TOKEN is an Automation token (not a user token requiring OTP) to avoid EOTP failures.
- Retry Logic for Registry Propagation: Verifies published versions with bounded retries to handle eventual consistency delays after npm publish.
- Draft Release Detection Guardrails: Promotes publishing only from GitHub release events that actually fire (e.g., release published), and adds checks for workflow_dispatch scenarios.
- Build Script Protection: Requires SKIP_BUILD_BUMP=1 during release builds to avoid silent version mutation from bump-build scripts.
Quick Start
Ask an AI to generate a GitHub Actions workflow step-by-step that applies semver validation, verifies NPM_TOKEN is automation-grade, retries npm verification up to 5 times with 15-second intervals, and only proceeds on release-published events while setting SKIP_BUILD_BUMP=1 for release builds.