Agent skill
bump-version
Bump the version of the zenoh-ros2-sdk package across all configuration files. Use when the user asks to update, bump, or change the package version, or when preparing a new release.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/bump-version
SKILL.md
Bump Version
This skill guides you through upgrading the version number of the zenoh-ros2-sdk package.
When to Use
- User asks to "bump", "update", or "change" the version
- Preparing a new release (major, minor, or patch)
- Version numbers are out of sync across config files
1. Determine the New Version
Decide whether this is a Major, Minor, or Patch release.
- Current Version: Check
pyproject.tomlorzenoh_ros2_sdk/__init__.py. - Example:
0.1.2->0.1.3(Patch)
2. Update Files
You must update the version string in the following 3 files. Ensure they all match exactly.
A. pyproject.toml
Update the version field under [project]:
[project]
name = "zenoh-ros2-sdk"
version = "0.1.3" # <--- Update this
B. zenoh_ros2_sdk/__init__.py
Update the __version__ variable:
__version__ = "0.1.3" # <--- Update this
C. setup.py
Update the version argument in the setup() call:
setup(
name="zenoh-ros2-sdk",
version="0.1.3", # <--- Update this
# ...
)
3. Verify Changes
Run the following command to verify consistency:
python3 setup.py --version
The output must match your new version.
4. Commit Changes
Commit the changes with a standard message:
git add pyproject.toml setup.py zenoh_ros2_sdk/__init__.py
git commit -m "bump(version): update version to 0.1.3"
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?