skills.rest
Boise-State-Development
Boise-State-DevelopmentOFFICIAL
Explore all skills by this author →
GitHub

version

Bump the VERSION file and sync package manifests for consistent SemVer.

16|27|Updated Nov 29, 2025
Search Tags:#versioning#monorepo#manifests#semver#release-management#ci-cd#version-bump
One-click install
npx skills add https://github.com/Boise-State-Development/agentcore-public-stack --skill version-boise-state-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: version
Source: https://github.com/Boise-State-Development/agentcore-public-stack/tree/main/.claude/skills/versioning
Command: npx skills add https://github.com/Boise-State-Development/agentcore-public-stack --skill version-boise-state-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of bumping and syncing the repository version across manifests, ensuring consistent SemVer-based releases.

Core Features & Use Cases

  • Bump major, minor, or patch versions by editing the VERSION file at the repo root.
  • Run the version synchronization script to update frontend/backend manifests and other package manifests.
  • Use in release pipelines to enforce version consistency across deployments.

Quick Start

Bump the version by editing the VERSION file and run the sync script to update manifests.

Frequently Asked Questions about version

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

FAQPage Schema
How do I automate SemVer version bumps across a monorepo?▼

To automate SemVer version bumps across a monorepo, edit the root VERSION file and run the repository's sync script to automatically update manifests across all packages.

What is the best way to sync package versions for a release pipeline?▼

Syncing package versions for a release pipeline requires bumping the VERSION file and executing the sync-version script to enforce consistent SemVer across backend, frontend, and infrastructure manifests.

How does manifest synchronization work during monorepo releases?▼

Manifest synchronization works by running the scripts/common/sync-version.sh script after updating the VERSION file, propagating the new SemVer number to all frontend and backend package manifests.

Do I need a specific file structure to enforce version consistency in CI?▼

Yes, enforcing version consistency in CI requires a VERSION file at the repository root and the specific sync script located at scripts/common/sync-version.sh to properly bump and sync manifests.

Can I bump major, minor, and patch versions independently for monorepo deployments?▼

Yes, you can bump major, minor, or patch versions independently by modifying the VERSION file at the repo root before triggering the synchronization script for cross-package deployment consistency.

Related Skills

Explore More Software Engineering Skills→
jperezdelrealjperezdelreal

distributed-mesh

Generate mesh.json manifests and copy sync scripts for distributed squad coordination.

Community
Intermediate
monomono
5.5k

release-publish

Publish SkiaSharp packages to NuGet.org and finalize releases.

Official
Advanced
SPANDigitalSPANDigital

release-pycel2sql

Automate version tagging, building, and publishing to PyPI for pycel2sql.

Official
Intermediate
snow-jallensnow-jallen

release-process

Automate version bumps, tags, GitHub releases, and npm publishing for Squad.

Community
Advanced