bump-version

Automates updating DecentPaste's version numbers in multiple config files via shell commands.

232|8|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/decentpaste/decentpaste --skill bump-version-decentpaste
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-version
Source: https://github.com/decentpaste/decentpaste/tree/main/.claude/skills/bump-version
Command: npx skills add https://github.com/decentpaste/decentpaste --skill bump-version-decentpaste

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually updating version numbers across various config files can be time-consuming and error-prone. This skill automates the process, ensuring consistency without the need for building.

Core Features & Use Cases

  • Automated Version Bumping: Updates the version number in package.json, Cargo.toml, tauri.conf.json, and downloads.json with a single command.
  • Supports Multiple Platforms: Works for Windows, macOS, Linux, Android, and iOS builds.
  • Use Case: When preparing for a new release, you can use this skill to update the version numbers across all config files to reflect the new version.

Quick Start

Run the command 'bump-version' to update version numbers in all DecentPaste config files.

Frequently Asked Questions about bump-version

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

FAQPage Schema
How do I automate version bumps across multiple configuration files?

Automated version bumping updates version numbers across files like package.json, Cargo.toml, and tauri.conf.json with a single command, ensuring consistency without manual editing or building.

What is the best way to update version numbers for a multi-platform release?

Updating version numbers for multi-platform releases is handled by modifying configuration files directly using shell commands, supporting builds across Windows, macOS, Linux, Android, and iOS.

Which configuration files are supported by automated version bumping?

Automated version bumping supports updating version strings in package.json, Cargo.toml, tauri.conf.json, and downloads.json for the DecentPaste application release workflow.

Can I use shell commands to update version control configurations without rebuilding?

Shell commands directly modify file contents to apply version control updates, allowing you to bypass the building process entirely while maintaining version consistency across config files.

Why is manual version bumping error-prone for release management?

Manual version bumping is error-prone because updating version numbers individually across various config files takes time and risks inconsistency, which automation solves by applying changes uniformly.

Does automated version bumping work with Tauri configuration files?

Automated version bumping works with Tauri configuration files by directly modifying tauri.conf.json alongside other config files to reflect the new version for release management.