skills.rest
barichter
barichterCOMMUNITY
Explore all skills by this author →
GitHub

versioning-policy

Enforce strict Semantic Versioning and synchronize versions across Squad SDK and CLI packages.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that the Squad SDK and CLI maintain consistent versioning across all packages, preventing version mismatches and prerelease leaks.

Core Features & Use Cases

  • Strict Semver: Enforces the use of strict Semantic Versioning for all packages.
  • Prerelease Version Management: Controls the creation and use of prerelease versions for local development testing.
  • Version Synchronization: Ensures that the SDK, CLI, and root package.json files have identical versions.
  • CI Enforcement: Blocks PRs containing prerelease versions in package.json files to prevent deployment issues.

Quick Start

Confirm the versioning rules by running the 'versioning-policy' skill and review the guidelines.

Frequently Asked Questions about versioning-policy

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

FAQPage Schema
How do I synchronize npm package versions across a monorepo?▼

You can synchronize npm package versions by enforcing strict Semantic Versioning rules that keep the SDK, CLI, and root package.json files on identical versions. This prevents version mismatches across your packages.

How do I prevent prerelease versions from leaking into production deployments?▼

To prevent prerelease version leaks, you can configure CI gate configurations that block pull requests containing prerelease versions in package.json files. This ensures only stable releases merge.

What is strict Semantic Versioning and when do I need it for package management?▼

Strict Semantic Versioning enforces standardized version bumping for local development and production packages. You need it to maintain version synchronization and prevent mismatches across interconnected SDK and CLI packages.

How do I manage prerelease versions for local development testing?▼

You manage prerelease versions by controlling their creation and use specifically for local development testing, while relying on CI enforcement to block these prerelease versions from updating the main package.json files.

Can I use this versioning policy to automate version bumps in CI?▼

Yes, the versioning policy supports CI environments by providing strict version bump processes and CI gate configurations. These configurations enforce version synchronization and block invalid prerelease package versions.

Why do my Squad SDK and CLI packages keep getting version mismatches?▼

Version mismatches happen when SDK, CLI, and root package.json files are updated independently. Implementing strict version synchronization ensures all packages maintain identical versions and prevents these inconsistencies.

Related Skills

Explore More Software Engineering Skills→
z4nr34lz4nr34l

turborepo

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

Community
Advanced
pwarnockpwarnock
2

release-publishing

Automate release planning and publishing workflows with Changesets and semantic versioning.

Community
Intermediate
arbazkhan971arbazkhan971
26

devsecops

Integrate security scanning into CI/CD pipelines with blocking gates.

Community
Advanced
mrsorbatemrsorbate

github-release-management

Orchestrate GitHub release workflows with semantic versioning and multi-platform builds.

Community
Advanced