release

Coordinate version bumps, changelog updates, verification, tagging, and pushes for Rust/Cargo releases.

29|2|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/agentty-xyz/agentty --skill release-agentty-xyz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/agentty-xyz/agentty/tree/main/skills/release
Command: npx skills add https://github.com/agentty-xyz/agentty --skill release-agentty-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies and streamlines the multi-step release process for the repository so maintainers can reliably bump versions, update changelogs, run validation checks, tag releases, and publish artifacts without missing steps.

Core Features & Use Cases

  • Structured Version Bumping: Guide the user to choose a semantic version bump (major, minor, patch) and update the Cargo.toml and Cargo.lock appropriately.
  • Verification & CI Preparation: Ensure prek validation hooks, linters, and tests run before tagging to prevent regressions.
  • Changelog & Contributors: Produce a Keep a Changelog-compatible entry for the new version and generate a contributor list from commit metadata.
  • Tagging and Publishing: Create a v-prefixed git tag, push commits and tags to origin, and rely on GitHub Actions to create the release artifacts.
  • Use Case: Preparing a new release for a Rust/Cargo workspace where you must validate builds, update docs, and publish a semantically versioned release.

Quick Start

Bump the version to patch, update Cargo.toml and CHANGELOG.md, run prek validation hooks, create a v-prefixed git tag, and push the commit and tag to origin.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate semantic versioning and changelog updates for a Cargo project?▼

Automating semantic versioning for a Cargo project involves coordinating version bumps in Cargo.toml and Cargo.lock, generating Keep a Changelog entries, and creating v-prefixed git tags before pushing to origin.

What's the best way to prepare a Rust workspace for a semantic version release?▼

Preparing a Rust workspace for a semantic version release requires running prek validation hooks and tests, updating Cargo.lock, generating contributor lists from commits, and tagging before pushing.

Can I use GitHub Actions to publish release artifacts after creating a git tag?▼

Yes, you can use GitHub Actions to publish release artifacts after pushing commits and v-prefixed git tags to origin, relying on CI to create the final release artifacts automatically.

How does generating a contributor list from git commits work during versioning?▼

Generating a contributor list during versioning extracts commit metadata to identify authors, producing a Keep a Changelog-compatible entry that credits contributors for the new release.

Do I need prek hooks to validate my Rust project before bumping versions?▼

Yes, running prek validation hooks before version bumping ensures linters and tests pass, preventing regressions from being tagged in the semantic version release.

Why should I update both Cargo.toml and Cargo.lock when releasing a new version?▼

Updating both Cargo.toml and Cargo.lock when releasing a new version ensures workspace dependency locks match the bumped semantic version, preventing build inconsistencies during release validation.