bumpup-versions
Skill1 starsChanged 9 months agoApache-2.0View on GitHub
Consistently bump and synchronize versions across all packages in the monorepo using pnpm. Use this to ensure the root and all workspace packages share the same version number.
- Installs packages
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/tech-stack.mdcCursor rule
- build-and-fixSkill
- clean-projectSkill
- fix-issueSkill
- improve-claude-configSkill
- initialize-projectSkill
- lint-and-fixSkill
- manage-adrSkill
- manage-changelogSkill
- node-upgradeSkill
- security-vulnerability-auditSkill
- setup-dev-envSkill
- sync-readmeSkill
- test-and-fixSkill
- test-integration-dockerSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
When preparing for a release that requires a unified version bump across all packages.
- Very specific: line 13
When you notice version drift between the root package.json and workspace packages.
- Distinctive: line 14
When requested to "bump versions", "release a new version", or "sync package versions".
- Very specific: line 24
Run the version command recursively across all packages in the workspace using pnpm -r exec.
- Very specific: line 32
Update the root package.json to match the workspace versions.
- Very specific: line 40
Run pnpm install to ensure pnpm-lock.yaml is updated with the new versions and any internal workspace dependencies (using workspace:*) are …
- Very specific: line 48
Check a sample of package.json files to ensure they all reflect the new version.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bumpup Versions Skill
This skill provides a standardized workflow to synchronize and increment version numbers across the entire monorepo (root and all packages) using native pnpm commands.
When to Use
- When preparing for a release that requires a unified version bump across all packages.
- When you notice version drift between the root
package.jsonand workspace packages. - When requested to "bump versions", "release a new version", or "sync package versions".
Instructions
1. Determine Target Version
Identify if you are performing a semantic bump (patch, minor, major) or setting an explicit version (e.g., 1.0.0).
2. Synchronize Workspace Packages
Run the version command recursively across all packages in the workspace using pnpm -r exec. The --no-git-tag-version flag prevents automatic git tagging and commits, and --allow-same-version ensures it doesn't fail if a package is already at the target version.
pnpm -r exec pnpm version <version_or_bump_type> --no-git-tag-version --allow-same-version3. Update Root Version
Update the root package.json to match the workspace versions.
pnpm version <version_or_bump_type> --no-git-tag-version --allow-same-version4. Update Lockfile and Internal References
Run pnpm install to ensure pnpm-lock.yaml is updated with the new versions and any internal workspace dependencies (using workspace:*) are correctly resolved.
pnpm install5. Verify Changes
Check a sample of package.json files to ensure they all reflect the new version.
grep '"version":' package.json packages/*/package.json packages/plugins/*/package.jsonTermination Criteria
- The
versionfield in the rootpackage.jsonmatches the target version. - The
versionfield in allpackages/**/package.jsonfiles matches the target version. pnpm-lock.yamlhas been updated and there are no linting/test regressions related to the version change.
Examples
Scenario: Performing a patch bump across the monorepo
- Agent: "I will bump the version to the next patch."
- Command:
pnpm -r exec pnpm version patch --no-git-tag-version --allow-same-version - Command:
pnpm version patch --no-git-tag-version --allow-same-version - Command:
pnpm install - Verification:
grep '"version":' package.json packages/*/package.json
Scenario: Setting an explicit version (e.g., 0.2.0)
- Agent: "Synchronizing all packages to version 0.2.0."
- Command:
pnpm -r exec pnpm version 0.2.0 --no-git-tag-version --allow-same-version - Command:
pnpm version 0.2.0 --no-git-tag-version --allow-same-version - Command:
pnpm install
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

