Release Process

Validate package manifests and enforce release rules for npm monorepo publishes.

9|1|Updated Jul 21, 2025
One-click install
npx skills add https://github.com/usepowershell/PoshMcp --skill release-process-usepowershell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Release Process
Source: https://github.com/usepowershell/PoshMcp/tree/main/.squad/templates/skills/release-process
Command: npx skills add https://github.com/usepowershell/PoshMcp --skill release-process-usepowershell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies a battle-tested release process that prevents broken npm publishes caused by workspace leaks, incorrect publish commands, improper npm tokens, draft releases, or invalid version formats, and reduces long recovery windows after failed releases.

Core Features & Use Cases

  • Pre-publish validation: Scan packages/*/package.json for file:/link: references, absolute paths, and non-semver versions to stop faulty publishes before they start.
  • Safe publish commands: Enforce per-package cd && npm publish --access public usage instead of workspace-scoped or -w publishes that hang with 2FA.
  • Fallbacks and verification: Define one-retry fallback to local publish, post-publish smoke tests, CI publish-policy gating, and guidance on automation tokens and GitHub release behavior.
  • Use case: Release managers and CI pipelines for a monorepo can run these checks to ensure reliable promotion from dev→preview→main and successful npm and GitHub Release workflows.

Quick Start

Run the pre-publish validation across packages, then cd into each package directory and publish with npm publish --access public, and finally perform the post-publish smoke test to verify the release.

Frequently Asked Questions about Release Process

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

FAQPage Schema
How do I prevent broken npm publishes in a monorepo?

Prevent broken npm publishes by validating package manifests for file: or link: dependencies and enforcing per-package publish commands across the monorepo before release.

Why does npm publish hang with 2FA in a monorepo workspace?

Workspace-scoped npm publish commands hang with 2FA because they route authentication incorrectly. Enforce per-package cd && npm publish --access public usage to avoid this issue.

How do I validate package.json for file:/link: references before release?

Run pre-publish validation across packages/*/package.json to scan for file:/link: references, absolute paths, and non-semver versions, stopping faulty publishes before they start.

Do I need an automation-type npm token for CI package publishing?

Yes, CI publish-policy gating requires an automation-type npm token to ensure reliable package promotion and prevent authentication failures during automated release workflows.

What is the best way to run a post-publish smoke test after an npm release?

Run a post-publish smoke test to verify the release after executing one-retry fallback to local publish, ensuring the published package is functional and the release is successful.

How do I stop draft releases on GitHub when publishing npm packages?

Enforce release rules that prohibit draft releases and validate version formats to ensure successful npm and GitHub Release workflows without long recovery windows.