release

Update version references and CHANGELOG, run pre-flight checks, and open a release PR.

4|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/Taketo-Yoda/uv-sbom --skill release-taketo-yoda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Taketo-Yoda/uv-sbom/tree/main/.claude/skills/release
Command: npx skills add https://github.com/Taketo-Yoda/uv-sbom --skill release-taketo-yoda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the release preparation workflow by consistently bumping versions across multiple files, updating CHANGELOG formatting, and opening a PR to main, reducing manual toil and potential errors.

Core Features & Use Cases

  • Update version numbers in all required files: Cargo.toml, python-wrapper/pyproject.toml, and python-wrapper/uv_sbom_bin/install.py
  • Update CHANGELOG.md to insert a new version section and preserve a proper Unreleased workflow
  • Run pre-flight checks including cargo fmt, cargo clippy, and cargo test before releasing
  • Create a release branch and PR to main to enable controlled, auditable releases
  • Use case: teams releasing Rust and Python components with aligned versioning and changelog documentation
  • Use case: automation pipeline where release readiness depends on passing checks and correct version propagation

Quick Start

Specify the target version (e.g., 1.2.0) to automatically bump versions, update CHANGELOG, run pre-flight checks, and open a release PR to main.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumping across multiple files like Cargo.toml and pyproject.toml for a release?

Automate version bumping by updating version references across multiple files like Cargo.toml, pyproject.toml, and install.py simultaneously. This ensures version consistency and reduces manual toil when preparing a new release for Rust and Python ecosystems.

How does changelog automation work when preparing a release PR?

Changelog automation updates CHANGELOG.md by inserting a new version section while preserving the Unreleased workflow. It formats entries correctly before generating a PR to main, ensuring auditable and properly documented release histories.

Can I enforce pre-flight checks like cargo fmt, clippy, and test before opening a release PR?

Pre-flight checks including cargo fmt, cargo clippy, and cargo test are enforced during the release process. This validates branch rules and ensures release readiness before creating a release branch and opening a PR to main.

What is the best way to manage release readiness for aligned Rust and Python components?

Managing release readiness for aligned Rust and Python components involves propagating correct versions across multi-file ecosystems and enforcing passing pre-flight checks. This controlled process reduces potential errors before generating a release PR to main.

Does this release automation workflow require passing all checks before creating a PR to main?

Release automation requires passing pre-flight checks like cargo fmt, clippy, and test before creating a release branch and PR to main. This controlled approach ensures version consistency and code quality for teams enforcing pre-release validation.