whalefall-version-update

Automate Python project-wide version updates across files and documentation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nyealovey/WhaleFall --skill whalefall-version-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: whalefall-version-update
Source: https://github.com/nyealovey/WhaleFall/tree/main/skills/public/whalefall-version-update
Command: npx skills add https://github.com/nyealovey/WhaleFall --skill whalefall-version-update

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the common issue of version drift across a codebase, ensuring that the application's version number is consistently updated in all critical locations during releases.

Core Features & Use Cases

  • Automated Version Bumping: Updates version numbers in app/settings.py, pyproject.toml, env.example, and uv.lock.
  • Documentation Sync: Ensures README.md, CHANGELOG.md, and app/templates/about.html reflect the new version.
  • Deployment Script Updates: Modifies version information in deployment scripts.
  • Use Case: Before releasing a new version of WhaleFall, use this Skill to automatically update the version number everywhere it appears, preventing inconsistencies and ensuring accurate reporting.

Quick Start

Use the whalefall-version-update skill to update the version to 1.5.1 and set the release theme to "Initial production release".

Frequently Asked Questions about whalefall-version-update

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

FAQPage Schema
How do I synchronize version numbers across a Python project's pyproject.toml, uv.lock, and documentation?

To synchronize version numbers across a Python project, this Skill automates updating pyproject.toml, uv.lock, env.example, README, CHANGELOG, and deployment scripts simultaneously. It prevents version drift by ensuring all files reflect the new release.

What is the best way to automate version bumps for APP_VERSION and avoid version drift in a codebase?

Automating version bumps for APP_VERSION prevents version drift by systematically applying new release numbers across settings, lock files, and documentation. This approach replaces manual edits, ensuring accurate and consistent version reporting throughout the codebase.

How do I update CHANGELOG and README versions automatically when preparing a Python release?

Updating CHANGELOG and README versions automatically is handled by running the Skill's version synchronization process before a release. It modifies documentation files alongside code configurations to ensure your README and CHANGELOG reflect the new version accurately.

Does this version synchronization approach work with uv.lock and deployment scripts?

Yes, this version synchronization approach works with uv.lock and deployment scripts by directly modifying version information within these files. It targets Python project environments utilizing uv for dependency management and includes deployment script updates.

What files are affected when updating a Python project's version number for a release?

Updating a Python project's version number affects app/settings.py, pyproject.toml, env.example, uv.lock, deployment scripts, README.md, CHANGELOG.md, and about.html templates. The Skill ensures all these specific files receive the version bump.

Are there self-checking scripts to verify version consistency after a release update?

Yes, self-checking scripts are included to verify version consistency after a release update. The Skill provides commit and PR templates alongside these checks to streamline the release workflow and catch any synchronization errors.