ci-validation-gates

To validate semver format in GitHub Actions, you add a defensive CI gate that checks version strings before publish, preventing npm mangling and invalid tags. This stops broken releases caused by misconfigured versioning.

Your npm publish workflow fails because user tokens with 2FA block automated CI publishing. You need a gate that enforces npm Automation tokens instead of user tokens, enabling seamless CI publishing without manual intervention.

To prevent GitHub Actions workflows from triggering on draft releases, implement a draft-release detection gate that ensures workflows trigger only on published releases, not drafts or pre-releases, guarding against premature deployments.

The best way to handle eventual consistency in npm registries is implementing retry logic after publish. This propagation check retries verification steps to ensure the published artifact is actually available before proceeding.

No, you do not need any dependencies to add defensive CI gates. This skill provides explicit gates and scripts to validate semver, ensure automation tokens, implement retry logic, and guard build steps directly in GitHub Actions.

To stop broken release deployments, enforce defensive CI/CD practices like semver validation, npm automation token verification, retry propagation for registry consistency, and draft-release detection across your GitHub Actions workflows.