developer-bump-version

Bump the Earth2Studio package version and insert a blank CHANGELOG section on main.

1.1k|251|Updated Apr 5, 2024
One-click install
npx skills add https://github.com/NVIDIA/earth2studio --skill developer-bump-version
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer-bump-version
Source: https://github.com/NVIDIA/earth2studio/tree/main/.claude/skills-dev/developer-bump-version
Command: npx skills add https://github.com/NVIDIA/earth2studio --skill developer-bump-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a release branch is merged into main, the repository still carries the old version string, blocking further development commits. This Skill automates the version bump and CHANGELOG housekeeping needed to start a new development cycle on main.

Core Features & Use Cases

  • Version Computation: Reads earth2studio/__init__.py and computes the next minor alpha version (e.g., 0.16.0 to 0.17.0a0), detecting if the bump was already completed.
  • CHANGELOG Management: Inserts a blank section for the new development version and cleans up the released section (removing empty subsections, stripping alpha/rc suffixes, setting release dates).
  • Automated Hatch Bump: Runs uv run hatch version minor and uv run hatch version alpha, then commits and pushes the changes with confirmation gates at each step.
  • Use Case: After merging the 0.16.0 release branch, run this Skill to bump main to 0.17.0a0, add the blank CHANGELOG section, and push a version-bump-0.17.0a0 branch ready for a PR.

Quick Start

Use the developer-bump-version skill to bump the Earth2Studio version on main and start the new development cycle.

Frequently Asked Questions about developer-bump-version

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

FAQPage Schema
How do I bump the Earth2Studio version after a release?

Run this Skill on main after the release branch merges. It reads the current version from earth2studio/__init__.py, computes the next minor alpha, updates CHANGELOG.md, and runs hatch version minor followed by hatch version alpha.

How to start a new development cycle on main after merging a release branch?

Create a version-bump branch from main, insert a blank CHANGELOG section for the next alpha version, bump the package version with hatch, then commit and push. This Skill performs all these steps with confirmation gates.

What happens if the version was already bumped?

The Skill checks whether the version already ends in the expected alpha suffix and whether a CHANGELOG section for the target version exists. If the bump is complete, it informs you and stops without making changes.

Why does the pre-commit hook fail during the version bump commit?

The pyupgrade pre-commit hook can fail due to a Python version incompatibility. It is safe to skip it by committing with SKIP=pyupgrade, which the Skill notes when this occurs.

Does the version bump require a pull request?

If main is a protected branch, open a PR titled "Bump version to X.(Y+1).0a0" targeting main after pushing the branch. Otherwise, a direct push is sufficient.