version-management

Automate semantic versioning, changelog generation, and release tagging for software projects.

12|1|Updated Jul 15, 2025
One-click install
npx skills add https://github.com/majiayu000/sage --skill version-management-majiayu000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-management
Source: https://github.com/majiayu000/sage/tree/main/.sage/skills/version-management
Command: npx skills add https://github.com/majiayu000/sage --skill version-management-majiayu000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes version numbers, CHANGELOG creation, and release workflows to ensure consistent software release history.

Core Features & Use Cases

  • Semantic Versioning: Enforce MAJOR.MINOR.PATCH across all crates and packages.
  • Changelog Automation: Generate and maintain changelogs aligned with releases.
  • Release Workflow: Define tagging, publishing, and remediation steps for new versions.

Quick Start

To start using the version management process, update the version in Cargo.toml, run the release workflow to generate a changelog, tag the release, and push to repository.

Frequently Asked Questions about version-management

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

FAQPage Schema
How do I automate semantic versioning and changelog generation for a Rust project?

Automate semantic versioning by enforcing MAJOR.MINOR.PATCH formats in Cargo.toml files, generating a CHANGELOG, and defining a structured release workflow for tagging and publishing new versions.

What's the best way to manage consistent release histories across multiple Rust crates?

Manage consistent release histories across multi-crate setups by applying uniform semantic versioning, automating changelog generation, and standardizing the release tagging workflow for all packages.

How does semantic versioning work for multi-crate Rust repositories?

Semantic versioning for multi-crate repositories enforces MAJOR.MINOR.PATCH formats across all crates, updates individual Cargo.toml files, and generates a unified CHANGELOG aligned with each release.

Can I standardize release workflows and tagging for Rust packages using Cargo?

Standardize release workflows by defining structured tagging, publishing, and remediation steps for Rust packages, ensuring version updates in Cargo.toml are consistently pushed to the repository.

Do I need to manually update Cargo.toml versions before starting the release workflow?

Yes, to start the version management process, manually update the version number in Cargo.toml, then run the release workflow to generate the changelog, tag the release, and push to repository.