skills.rest
christianhelle
christianhelleCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release-process

Automates secure release publishing with SemVer checks, GitHub tagging, and npm rollback safeguards.

413|64|Updated Feb 7, 2023
Search Tags:#git#rollback#npm#release#semver#ci-cd#audit-trail
One-click install
npx skills add https://github.com/christianhelle/refitter --skill release-process-christianhelle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/christianhelle/refitter/tree/main/.copilot/skills/release-process
Command: npx skills add https://github.com/christianhelle/refitter --skill release-process-christianhelle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Step-by-step, auditable release runbook that prevents disasters during Squad deployments, ensuring compliance and traceability.

Core Features & Use Cases

  • Pre-release validations: semver checks, token verification, branch state, and skip flags to avoid problematic releases.
  • Release workflow guardrails: version bump, tagging, GitHub release publication, and automated verification with retry logic across npm registries.
  • Rollback and remediation: explicit unpublish, deprecation, and tag/release cleanup procedures.

Quick Start

Follow this runbook to execute a safe, auditable release from the main branch with built-in validations and rollback safeguards.

Frequently Asked Questions about release-process

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

FAQPage Schema
How do I automate npm publication with rollback safeguards from the main branch?▼

Automated npm publication with rollback safeguards enforces semver rules, validates pre-release conditions, bumps versions, tags commits, and publishes to the registry with explicit unpublish and deprecation paths.

What is the best way to enforce semver rules during a CI-CD release workflow?▼

Enforcing semver rules during a CI-CD release workflow involves pre-release validations for version bumps, branch state checks, and automated tagging with post-publish verification across npm registries.

How does a release runbook handle rollback and remediation for published npm packages?▼

A release runbook handles rollback and remediation by executing explicit unpublish procedures, applying package deprecation, and cleaning up tags and GitHub releases to restore the previous state.

Can I skip pre-release validations like token verification when running an automated npm release?▼

Pre-release validations including token verification, semver checks, and branch state checks cannot be skipped without explicit flags, ensuring problematic releases are avoided during deployments.

Why does my GitHub release publication fail during automated version bumps?▼

GitHub release publication fails during version bumps when draft-release checks identify unmet pre-release conditions, missing token verification, or incorrect branch state, halting the workflow automatically.

What are the limitations of automated end-to-end release governance for npm packages?▼

Automated release governance is limited to main-branch releases and requires functional compliance with pre-release validations, build-skip controls, and documented rollback procedures to prevent deployment disasters.

Related Skills

Explore More Software Engineering Skills→
elbrunoelbruno
2

ci-validation-gates

Enforce CI/CD gates validating semver, NPM_TOKEN, and release events.

Community
Advanced
vercelvercel
26.1k

list-npm-package-content

List npm package tarball contents before publishing.

Official
Intermediate
sudhakrmssudhakrms
1

release-process

Automate and govern software releases with validation and rollback procedures.

Community
Advanced
HazATHazAT
947

release

Automate versioned npm package releases with changelog generation and GitHub releases.

Community
Intermediate