bump

Synchronize version numbers across package.json, Tauri, and Cargo manifests for releases.

609|50|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/poco-ai/Agentero --skill bump-poco-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump
Source: https://github.com/poco-ai/Agentero/tree/main/.agents/skills/bump
Command: npx skills add https://github.com/poco-ai/Agentero --skill bump-poco-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing a new version of the Agentero app requires updating version numbers scattered across many files (package.json, tauri.conf.json, multiple Cargo.toml files, iOS project config). Manually editing each one is error-prone and can produce mismatched versions between the desktop installer, CLI, and release tag. ## Core Features & Use Cases - Unified Version Sync: Updates the version field in package.json, src-tauri/tauri.conf.json, src-tauri/Cargo.toml, crates/agentero-core/Cargo.toml, cli/Cargo.toml, and the iOS CFBundleShortVersionString/CFBundleVersion in one pass. - SemVer Validation: Verifies the target version is a valid SemVer string and stops to ask for clarification when the version argument is missing or ambiguous. - Release Safety Checks: Confirms Cargo.lock no longer holds stale local package versions, that agentero --version still derives from the CLI package version, and that release documentation rules remain consistent. - Use Case: When preparing release 0.1.3, invoke this Skill so every manifest is bumped together, minimal verification commands run, and you get a summary of changed files before creating the v0.1.3 tag. ## Quick Start Ask the agent to bump the project version to 0.1.3 using the bump skill and report the modified files and verification results.

Frequently Asked Questions about bump

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

FAQPage Schema
How do I bump the version of a Tauri app across all config files?

Update the version field in package.json, src-tauri/tauri.conf.json, and src-tauri/Cargo.toml together, plus any workspace crates and the iOS CFBundleShortVersionString. This Skill performs all edits in one pass and verifies consistency afterward.

How to keep Cargo workspace crate versions in sync during a release?

Edit the package version in each Cargo.toml (main crate, agentero-core, and CLI), then run cargo metadata to refresh Cargo.lock so no stale local package versions remain. The Skill automates this sequence and checks the lockfile.

Does the Android version need manual updating in a Tauri project?

No. Running tauri android build regenerates versionName and versionCode in src-tauri/gen/android/app/tauri.properties from the version in tauri.conf.json, so only the Tauri config needs editing.

What happens if I provide an invalid version number?

The Skill validates the target against SemVer rules before making changes. If the version is missing, malformed, or ambiguous, it stops and asks for a clear version instead of partially updating files.

Does this Skill create git tags or releases automatically?

No. It only modifies version fields and runs verification commands. Commits, v-prefixed tags, GitHub Releases, and pushes are left to the user unless explicitly requested.