ci-validation-gates

Validate semantic versions in a CI/CD pipeline by enforcing defensive patterns that check formatting before publishing. This prevents common versioning errors and ensures only valid versions are released to registries.

Registry propagation delays cause npm publish to fail when subsequent commands run before the registry updates. Implement retry logic in your CI/CD workflow to handle these delays and ensure reliable release processes.

Prevent CI/CD workflows from triggering on draft releases by implementing draft detection logic. This ensures your pipelines only execute on published releases, avoiding premature or invalid build deployments.

Secure release builds by verifying token types to ensure automation tokens are used instead of user tokens. Additionally, apply build script protection to safeguard against the mutation of release versions during execution.

Yes, you can add retry logic to CI/CD pipelines without external dependencies. The skill provides scripts to implement defensive patterns directly, handling propagation delays and securing workflows natively.

Mitigate security vulnerabilities in release workflows by applying defensive patterns including token type verification, version validation, and build script protection. These patterns safeguard against version mutation and unauthorized token usage.