release-process

Execute Squad release workflows from version bump to npm publish.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/lbouriez/Squad-Templates --skill release-process-lbouriez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/lbouriez/Squad-Templates/tree/main/Nectari-Devops-Squad/.copilot/skills/release-process
Command: npx skills add https://github.com/lbouriez/Squad-Templates --skill release-process-lbouriez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This runbook provides a definitive, auditable release process to prevent disasters during Squad releases.

Core Features & Use Cases

  • Enforces version bump, tag creation, and GitHub Release publishing in a single, auditable workflow.
  • Validates NPM_TOKEN type and ensures automation token usage, preventing OTP errors.
  • Includes rollback, deprecation, and post-publish verification steps to ensure published packages match versions and dist-tags.

Quick Start

Follow the runbook steps in this Skill to perform a complete Squad release from version bump to npm publication.

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 publish workflows with semver versioning across multiple workspaces?

Automate npm publish workflows by validating NPM_TOKEN types, enforcing branching rules, and applying semver version bumps across root and workspaces to ensure consistent tagging and prevent release disasters.

What is a fail-safe release checklist for npm packages and how does it prevent errors?

A fail-safe release checklist encodes validation steps, token handling, tagging, publishing, and rollback procedures. It prevents disasters by verifying NPM_TOKEN type and auditing versions and dist-tags across workspaces.

How do I create a GitHub Release and git tag for a multi-workspace npm project?

Create a GitHub Release and git tag by following an auditable runbook that enforces version bump, tag creation, and release publishing in a single workflow across root and workspaces to maintain release integrity.

Why does my npm publish workflow fail with OTP errors during a release?

npm publish workflows fail with OTP errors when using a standard NPM_TOKEN instead of an automation token. Validating token type and ensuring automation token usage prevents these errors during version bump and publish steps.

Can I rollback a published npm package version after a failed CI/CD release?

You can rollback a published npm package version after a failed release by following encoded rollback and deprecation procedures, then running post-publish verification checks to confirm dist-tags match expected versions.