version-management

Automate version bumping across project files with npm scripts.

Updated Dec 5, 2025

Search Tags:#software development #continuous integration #project maintenance #version management #version bumping

Ready to run

npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill version-management-apothecaryman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: version-management
Source: https://github.com/ApothecaryMan/pharmaflow-ai/tree/main/.agent/skills/version-management
Command: npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill version-management-apothecaryman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually updating version numbers across multiple project files can be time-consuming and prone to error. This skill streamlines the process for automated version bumping, ensuring consistency and accuracy.

Core Features & Use Cases

Automated Version Bumping: Handles updates to package.json, package-lock.json, and public/version.json with a single command.
Consistency Check: Ensures package.json and version.json match to avoid version mismatches.
Automated Cleanup: Clears localStorage to maintain user experience post-version change.

Quick Start

To raise the version, run the command: bump-version

Frequently Asked Questions about version-management

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

FAQPage Schema

How do I automate version bumping across multiple project files?▼

Automated version bumping updates version numbers across multiple project files simultaneously. You can run a single command to modify your package.json, package-lock.json, and version.json, ensuring consistency and accuracy throughout your software project.

Why does version mismatch happen between package.json and version.json?▼

Version mismatch happens when developers manually update version numbers independently across different files. Using an automated version bumping script checks that package.json and version.json match, avoiding discrepancies and maintaining data persistence consistency.

What is the best way to clear localStorage for user data persistence post-version change?▼

The best way to clear localStorage after a version change is to use an automated cleanup script. The version bumping process handles this automatically, clearing localStorage to maintain user experience and avoid stale data conflicts.

Do I need npm to run automated version bumping scripts?▼

Yes, you need npm and associated project scripts to run automated version bumping. The script relies on the npm environment to execute commands that modify versioning files and clear localStorage efficiently.

How to raise the version number in a ZINC project?▼

To raise the version number in a ZINC project, run the bump-version command. This executes the project scripts required to update package.json, package-lock.json, and public/version.json in one action.

Can I use version bumping scripts for continuous integration workflows?▼

Yes, you can integrate version bumping scripts into continuous integration workflows. Automating version updates ensures project maintenance consistency by synchronizing package files before deployment without manual intervention.