release-process

Orchestrates multi-stage software release with version validation, git tagging, and npm publication.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill release-process-jonnymuir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.copilot/skills/release-process
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill release-process-jonnymuir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires semver.

What problem does it solve?

This Skill eliminates the risk of human error, versioning disasters, and failed deployments by providing a strictly validated, step-by-step runbook for the Squad release process.

Core Features & Use Cases

  • Semver Validation: Automatically enforces strict 3-part semantic versioning to prevent npm registry mangling.
  • Automated Workflow Guardrails: Ensures correct token configuration, branch state, and build environment settings before any release action is taken.
  • Use Case: Use this Skill to safely coordinate a multi-package release, ensuring that the SDK and CLI are published to npm with the correct tags and verified via smoke tests.

Quick Start

Execute the release-process skill to validate the current environment and begin the automated version bump and deployment sequence.

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 deployment with semantic versioning validation?

Multi-package release automation coordinates SDK and CLI publication to npm with correct tags while running post-deployment smoke tests. It orchestrates version validation, git tagging, and npm publication across multiple packages to ensure release consistency.

What environment checks are required before running an automated npm release in GitHub Actions?

Automated npm releases require token security verification, branch state validation, and build environment settings confirmation before taking any release action. These workflow guardrails ensure correct configuration and prevent failed deployments caused by misconfigured CI/CD pipelines.

How do I prevent versioning errors when publishing multiple npm packages in a CI/CD pipeline?

Prevent versioning errors by enforcing strict adherence to semantic versioning through automated validation before any git tagging or npm publication. This eliminates human error and ensures packages are published with correctly formatted version numbers.

Does the release process support post-deployment smoke testing for npm packages?

Post-deployment smoke testing is supported as part of the automated deployment verification sequence. After npm package publication, the release process runs smoke tests to verify the deployment succeeded and the published packages are functional.