version-bump

Bump workspace package versions in a pnpm monorepo via JSON.

Updated Dec 29, 2025

Search Tags:#automation #workspace #pnpm #monorepo #package.json #semver #version

Ready to run

npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill version-bump-yu-iskw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: version-bump
Source: https://github.com/yu-iskw/dbt-artifacts-parser-ts/tree/main/.claude/skills/version-bump
Command: npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill version-bump-yu-iskw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps versions in sync across the monorepo by updating all top-level "version" fields in workspace package.json files, supporting a unified semver or two-line release strategy (parser/root vs dbt-tools).

Core Features & Use Cases

Read and present a version matrix for each relevant package.json.
Choose a bump model: unified across all packages or two separate lines (parser + root vs @dbt-tools/*).
Compute target versions from a base version, support exact versions or patch/minor/major increments, and apply changes.
Update only the files that carry a top-level version and verify the results.
Handle release workflows and guardrails to avoid mismatches between packages.

Quick Start

Ask it to bump all workspace package versions according to a selected strategy and apply the changes.

Frequently Asked Questions about version-bump

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

FAQPage Schema

How do I bump package versions across a pnpm monorepo?▼

To bump package versions across a pnpm monorepo, this Skill updates the top-level version fields in workspace package.json files. It interactively applies semantic increments or specific versions while keeping all packages in sync.

Can I apply a unified versioning strategy to multiple packages in a workspace?▼

Yes, you can apply a unified versioning strategy to multiple workspace packages. The Skill supports a unified model across all packages or a two-line strategy to manage different release tracks like parser and tools separately.

How does semantic versioning work for monorepo package.json files?▼

Semantic versioning for monorepo package.json files works by computing target versions from a base version. The Skill applies exact versions or patch, minor, and major increments exclusively to files carrying a top-level version field.

Do I need pnpm to manage workspace package versions?▼

Yes, you need pnpm installed to manage workspace package versions with this Skill. It requires the pnpm environment to read the workspace configuration, compute new versions, and verify the applied changes.

What is the best way to handle a two-line release strategy in a monorepo?▼

The best way to handle a two-line release strategy is using the Skill's built-in model to separate versioning tracks, such as parser and root versus tools packages, ensuring targeted semantic increments without mismatches.