skills.rest
firstloophq
firstloophqOFFICIAL
Explore all skills by this author →
GitHub

version-bump

Increment CFBundleShortVersionString and CFBundleVersion in macOS Info.plist files.

9|3|Updated Jan 13, 2026
Search Tags:#automation#versioning#macos#semver#release-management#Info.plist#build-number
One-click install
npx skills add https://github.com/firstloophq/nomendex --skill version-bump-firstloophq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: version-bump
Source: https://github.com/firstloophq/nomendex/tree/main/.claude/skills/version-bump
Command: npx skills add https://github.com/firstloophq/nomendex --skill version-bump-firstloophq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Increment app version numbers and prepare releases by updating the Info.plist and ensuring build metadata stays consistent.

Core Features & Use Cases

  • Read current version data, increment CFBundleShortVersionString and CFBundleVersion, and apply changes automatically.
  • Ensure semantic versioning across alpha/beta/pre-release and final releases.
  • Use case: when preparing a new release, quickly bump the displayed version and build number.

Quick Start

Run the version-bump skill to increment the next release version in mac-app/macos-host/Info.plist.

Frequently Asked Questions about version-bump

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

FAQPage Schema
How do I increment CFBundleShortVersionString and CFBundleVersion in Info.plist for a macOS release?▼

To increment CFBundleShortVersionString and CFBundleVersion, the skill reads mac-app/macos-host/Info.plist, applies semantic versioning rules, updates both version fields, and writes the changes back to the file automatically.

What is the best way to automate semantic versioning for macOS app pre-releases like alpha and beta builds?▼

Automating semantic versioning for macOS pre-releases involves reading the current build metadata and applying specific increment rules for alpha, beta, or patch versions to ensure the build number and displayed version stay consistent across releases.

Does this versioning automation require any external dependencies or build tools to update Info.plist?▼

No external dependencies are required to update Info.plist, as the skill operates directly on the macOS app development workflow by reading and writing version changes to the file independently.

How do I prepare a macOS app release when the build number in Info.plist is out of sync with the displayed version?▼

Preparing a macOS app release with out-of-sync build numbers requires reading the current Info.plist data, incrementing both CFBundleShortVersionString and CFBundleVersion together, and applying the changes to ensure metadata consistency.

Can I use this skill to bump versions for both pre-release and final macOS app deployments?▼

Yes, you can bump versions for pre-release and final deployments, as the skill handles semantic versioning across alpha, beta, pre-release, and final releases while updating the necessary Info.plist fields.

Why does my macOS app version bump fail to apply semantic versioning rules to the Info.plist file?▼

A version bump fails to apply semantic versioning when the Info.plist path is incorrect or the existing CFBundleShortVersionString format does not match expected semantic versioning patterns for alpha, beta, or patch releases.

Related Skills

Explore More Software Engineering Skills→
anyekoutouminganyekoutouming
2

update-cursor-settings

Modify Cursor/VSCode settings.json values while preserving existing settings.

Community
Intermediate
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
DetrousDetrous
4

asc-xcode-build

Automate building, archiving, and exporting iOS/macOS apps with xcodebuild.

Community
Advanced
saajunaidsaajunaid

gh-cli

Automate GitHub CLI operations for issues, PRs, releases, and repos.

Community
Intermediate