skills.rest
nicolehaugen
nicolehaugenCOMMUNITY
Explore all skills by this author →
GitHub

versioning-policy

Manage monorepo package versions with strict Semantic Versioning rules.

Updated Apr 8, 2026
Search Tags:#versioning#version control#npm#package management#semver
One-click install
npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill versioning-policy-nicolehaugen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: versioning-policy
Source: https://github.com/nicolehaugen/CustomMetricsDashboard/tree/main/.squad/templates/skills/versioning-policy
Command: npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill versioning-policy-nicolehaugen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, and includes scripts (resource) components.

What problem does it solve?

This Skill addresses versioning discrepancies and pre-release leaks, ensuring smooth dependency resolution and consistent package versions in the Squad SDK and CLI.

Core Features & Use Cases

  • Semver Compliance: Enforces strict Semantic Versioning (Semver) for package versions.
  • Prerelease Management: Prevents the accidental commit of pre-release versions and ensures their ephemeral nature in local development.
  • Version Synchronization: Ensures SDK, CLI, and root package.json files have matching versions.

Quick Start

Run the bump-build.mjs script to increment the version in all package.json files to the next Semver level.

Frequently Asked Questions about versioning-policy

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

FAQPage Schema
How do I keep package versions synchronized across a monorepo?▼

To keep package versions synchronized across a monorepo, you can run a script that increments the version in all package.json files to the next Semver level, ensuring SDK, CLI, and root files match.

How do I prevent accidental pre-release version commits during local development?▼

To prevent accidental pre-release commits during local development, use a versioning policy that enforces the ephemeral nature of pre-releases, stopping them from being committed while allowing local testing.

Do I need npm workspaces to manage Semver in a JavaScript monorepo?▼

Yes, you need npm workspace setup to use this Semver management approach, as it relies on npm's workspace features to maintain consistency across multiple SDK and CLI packages.

What is the best way to enforce strict Semver compliance for SDK and CLI packages?▼

The best way to enforce strict Semver compliance for SDK and CLI packages is to use a versioning policy that automatically manages version increments and prevents discrepancies in dependency resolution.

Why do versioning discrepancies cause pre-release leaks in package management?▼

Versioning discrepancies cause pre-release leaks because inconsistent package versions disrupt smooth dependency resolution, allowing temporary local pre-releases to accidentally enter the main codebase.

Related Skills

Explore More Software Engineering Skills→
z4nr34lz4nr34l

turborepo

Configure Turborepo pipelines, caching, and per-package tasks in monorepos.

Community
Advanced
X-School-AcademyX-School-Academy
9

dev-swarm-npm-publish

Publish npm packages with semantic versioning and release notes.

Official
Advanced
louisbrulenaudetlouisbrulenaudet
18

pnpm

Manage pnpm workspace dependencies, catalogs, and Turborepo tasks in monorepos.

Community
Advanced
finger-gunfinger-gun
4

create-changesets

Generate semantic versioning changesets for pnpm monorepo packages.

Official
Advanced