skills.rest
Golnaz89
Golnaz89COMMUNITY
Explore all skills by this author →
Website𝕏@Golnaz89GitHub

release-process

Coordinate Squad releases with version validation, token checks, and GitHub publication.

Updated Jan 5, 2026
Search Tags:#automation#npm#release#semver#ci-cd#workflows#tagging
One-click install
npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill release-process-golnaz89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/Golnaz89/golnaz89.github.io/tree/main/.copilot/skills/release-process
Command: npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill release-process-golnaz89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Step-by-step release playbook designed to prevent release disasters by enforcing a strict, auditable process for Squad deployments.

Core Features & Use Cases

  • End-to-end release runbook covering version validation, token verification, branch hygiene, environment flags, and GitHub Releases.
  • Pre-flight checks ensure semver validity, proper NPM automation tokens, and clean git state before tagging.
  • Rollback and fallback procedures to deprecate or unpublish broken versions and revert changes safely.

Quick Start

Follow this runbook on a clean main branch to perform a safe release by starting with version validation and token checks.

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 package releases with strict semver validation?▼

To automate npm releases with semver validation, use a structured runbook that enforces pre-flight checks on version bumps, NPM tokens, and git state before tagging. This prevents deployment disasters by validating versions before publishing.

What checks are required before tagging a release in a CI/CD workflow?▼

Required pre-tagging checks in a CI/CD workflow include strict semver validation, NPM automation token verification, branch hygiene validation, and ensuring a clean git state. These pre-flight checks prevent broken versions from being tagged and published.

How do I bump versions across multiple package.json files for a release?▼

Bump versions across multiple package.json files by orchestrating a multi-step release workflow that synchronizes semver updates across all project packages. This structured process ensures version consistency before generating git tags and GitHub releases.

What is the best way to handle a broken npm package deployment?▼

The best way to handle a broken npm package deployment is to execute structured rollback and fallback procedures, which allow you to safely unpublish or deprecate broken versions and revert changes to restore stability.

Do I need an NPM automation token to publish GitHub releases?▼

Yes, you need an NPM automation token. The release process explicitly verifies your NPM_TOKEN during pre-flight checks to authenticate automated publishing and ensure secure package distribution before GitHub release publication.

Related Skills

Explore More Software Engineering Skills→
WayneWalterBerryWayneWalterBerry

release-process

Automate npm-based Squad releases with semver validation and rollback procedures.

Community
Advanced
sachinnair90sachinnair90

release-process

Coordinate safe software releases with semver, Git tags, GitHub Releases, and npm publication.

Community
Advanced
CHENyiru3CHENyiru3

managing-python-releases

Automate version bumps, changelog generation, and PyPI publishing for Python libraries.

Community
Advanced
p-o-ke-naep-o-ke-nae

changelog-automation

Generate changelogs from commits, pull requests, and releases.

Community
Advanced