skills.rest
acmeleme
acmelemeOFFICIAL
Explore all skills by this author →
GitHub

versioning-policy

Enforce strict semantic versioning across root and package packages.

Updated Nov 11, 2025
Search Tags:#workflow#versioning#npm#release#semver#ci#package-management
One-click install
npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill versioning-policy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: versioning-policy
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.squad/templates/skills/versioning-policy
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill versioning-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Version mismatches and prerelease leaks have caused production incidents when working with Squad SDK and CLI. This Skill codifies a centralized versioning policy to ensure consistent, release-ready versions across all packages.

Core Features & Use Cases

  • Strict semver enforcement across root and workspace packages to prevent -build.N prerelease leaks.
  • Synchronized version bumps via an automated process that updates root, sdk, and cli package.json files in lockstep.
  • CI enforcement via prerelease-version-guard to block prerelease versions from entering dev/main branches.
  • Ownership and governance with Surgeon as the maintainer of version changes.

Quick Start

Update all versions to a clean release across root and packages to align with the policy.

Frequently Asked Questions about versioning-policy

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

FAQPage Schema
How do I prevent prerelease versions from leaking into npm package releases?▼

Prevent prerelease leaks by enforcing strict semantic versioning across root and workspace packages using an automated prerelease-version-guard gate in CI to block -build.N prereleases from entering dev or main branches.

How do I synchronize version bumps across multiple npm workspace packages?▼

Synchronize version bumps across npm packages using an automated process that updates root, SDK, and CLI package.json files in lockstep to ensure all versions match and prevent mismatch incidents during releases.

What is strict semver enforcement for package management?▼

Strict semver enforcement applies a centralized versioning policy across root and workspace packages to ensure consistent, release-ready versions, preventing prerelease tags from accidentally entering production branches.

Does CI enforcement work with semantic versioning for pull requests?▼

Yes, CI enforcement applies the versioning policy during pull requests and releases, utilizing the prerelease-version-guard gate to block any mismatched or prerelease versions from being committed to protected branches.

Why do version mismatches cause production incidents in SDK and CLI releases?▼

Version mismatches cause incidents because prerelease versions and unsynchronized package.json files leak into production, which this versioning policy prevents by requiring synchronized bumps and strict semver across all packages.

Related Skills

Explore More Software Engineering Skills→
remix-runremix-run
33.3k

publish-placeholder-package

Publish a minimal placeholder npm package at version 0.0.0 to reserve the package name.

Official
Intermediate
deepfuturenowdeepfuturenow

publish-to-npm

Automate version bumps, builds, and npm publishing for @deepfuture packages.

Official
Advanced
RyoMurakami1983RyoMurakami1983
2

git-initial-setup

Automates GitLab project and repository setup for streamlined onboarding and management.

Community
Intermediate
michaelvolzmichaelvolz

rm-guide-config

Enforces centralized, script-driven conventions for repository build and package configuration changes.

Community
Basic