release-process

Automate version bumps, tags, GitHub releases, and npm publishing for Squad.

7|Updated Oct 24, 2020
One-click install
npx skills add https://github.com/snow-jallen/HomeSpeaker --skill release-process-snow-jallen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/snow-jallen/HomeSpeaker/tree/main/.copilot/skills/release-process
Command: npx skills add https://github.com/snow-jallen/HomeSpeaker --skill release-process-snow-jallen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This runbook provides a definitive, auditable protocol to prevent release disasters by standardizing steps, checks, and documentation across teams.

Core Features & Use Cases

  • Step-by-step pre-release validation (semver checks, token validation, branch/state checks) to ensure readiness before publishing.
  • Coordinated release workflow (version bumps, commit, tag, GitHub release, npm publish) with automated verification steps and rollback guidance.
  • Real-world guardrails and fallback procedures (rollback, deprecation, and common failure mitigation).

Quick Start

Follow the release runbook from Step 1 to Step 7 on the main branch to perform a compliant, automated release.

Frequently Asked Questions about release-process

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

FAQPage Schema
How do I automate a safe npm release workflow with git tags and version bumps?

An automated npm release workflow enforces semver validity, requires a clean git working tree, and coordinates version bumps, tag creation, and npm publishing. This ensures a safe, auditable release process with cross-package version synchronization.

What pre-release checks are needed before publishing an npm package?

Pre-release validation requires checking semver compliance, validating the Automation npm token, confirming a clean git working tree, and verifying cross-package version synchronization. These checks prevent release disasters by ensuring readiness before publishing.

How does cross-package version synchronization work during a release?

Cross-package version synchronization ensures all packages in a monorepo share consistent versions during a release. The process validates semver compliance across packages before bumping versions, committing changes, and creating git tags.

Do I need an Automation npm token to run an automated release process?

Yes, an Automation npm token is required to run the automated release process. It authenticates publishing rights during the npm publish step, ensuring the release is auditable and compliant with the enforced workflow.

What is the best way to handle a failed npm publish or release rollback?

A failed npm publish requires following rollback guidance and fallback procedures, including deprecating the published package version if necessary. The runbook provides specific mitigation steps for common release failure scenarios.

Can I run the release runbook from a dev branch or only the main branch?

The release runbook executes on the main branch to perform a compliant, automated release, but it also includes post-release verification on both main and dev branches to ensure cross-branch state consistency.