ci-validation-gates

Validate version formats, token types, and package propagation delays in CI/CD pipelines.

18|3|Updated Jul 3, 2020
One-click install
npx skills add https://github.com/jguadagno/jjgnet-broadcast --skill ci-validation-gates-jguadagno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-validation-gates
Source: https://github.com/jguadagno/jjgnet-broadcast/tree/main/.agents/skills/ci-validation-gates
Command: npx skills add https://github.com/jguadagno/jjgnet-broadcast --skill ci-validation-gates-jguadagno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need for secure, validated, and resilient CI/CD pipeline processes by enforcing version correctness, token validation, and handling propagation delays.

Core Features & Use Cases

  • Semver Validation: Checks release version formats before publishing to prevent invalid versioning errors.
  • Token Verification: Ensures use of appropriate automation tokens, avoiding errors caused by user tokens with 2FA.
  • Retry Logic: Implements multiple attempts to verify package publication, handling eventual consistency issues in registry propagation.
  • Draft Release Handling: Prevents workflows from triggering on draft releases, ensuring trigger accuracy.

Quick Start

Use the ci-validation-gates skill to automate validation steps before publishing a release by integrating its checks into your CI pipeline.

Frequently Asked Questions about ci-validation-gates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate semver validation in a CI/CD pipeline to prevent invalid release versioning errors?

Automate semver validation in a CI/CD pipeline by integrating scripts that check release version formats before publishing, ensuring release safety and preventing invalid versioning errors. This validates versions early in the workflow.

Why does my npm package publish workflow fail when using user tokens with 2FA, and how can I fix it?

Npm package publish workflows fail with user tokens due to 2FA restrictions. Fix this by implementing token verification to ensure use of appropriate automation tokens, avoiding errors caused by user tokens with 2FA.

How do I handle npm registry propagation delays and eventual consistency issues during package publication?

Handle npm registry propagation delays by implementing retry logic with multiple attempts to verify package publication, effectively managing eventual consistency issues in registry propagation during your release workflow.

What is the best way to prevent CI/CD workflows from triggering on draft releases?

Prevent CI/CD workflows from triggering on draft releases by applying draft release handling validation gates, ensuring trigger accuracy and stopping automated pipelines from acting on unpublished draft versions.

Do I need any dependencies to add retry mechanisms and validation gates to my npm automation scripts?

No dependencies are required to add retry mechanisms and validation gates to your npm automation scripts. The skill provides self-contained scripts for version validation, token verification, and retry logic without external dependencies.