release-rust-srec

Automate rust-srec release preparation with version bumps and release notes.

81|13|Updated Mar 18, 2025
One-click install
npx skills add https://github.com/hua0512/rust-srec --skill release-rust-srec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-rust-srec
Source: https://github.com/hua0512/rust-srec/tree/main/.claude/skills/release-rust-srec
Command: npx skills add https://github.com/hua0512/rust-srec --skill release-rust-srec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

rust-srec release management often involves coordinating version bumps, migrating notes across locales, and drafting a GitHub release body. This skill automates end-to-end release preparation to reduce manual toil and human error.

Core Features & Use Cases

  • Bump workspace version to the next semver and align downstream crates.
  • Promote staged unreleased notes into English and Chinese version pages, update indexes, and refresh release notebooks.
  • Reset unreleased notes after release and emit a ready-to-tag command for maintainers.

Quick Start

Prepare a new rust-srec release by selecting the next version and running the version bump workflow.

Frequently Asked Questions about release-rust-srec

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

FAQPage Schema
How do I automate rust-srec release preparation and version bumping?

Automating rust-srec release preparation involves bumping the workspace version in Cargo.toml, aligning downstream crates, and generating the rust-srec-vX.Y.Z tag command to streamline the maintainer workflow.

What is the best way to promote unreleased notes to versioned pages for a Rust release?

Promoting unreleased notes requires migrating staged content into English and Chinese versioned pages, updating the release-notes index and sidebar, and refreshing the release notebooks for the new version.

How do I generate a GitHub release body and tag command for rust-srec?

Generating a GitHub release body for rust-srec involves drafting the release notes from the promoted version pages and emitting a ready-to-tag command formatted as rust-srec-vX.Y.Z for maintainers to execute.

Can I reset unreleased notes automatically after cutting a new rust-srec version?

Resetting unreleased notes after cutting a new rust-srec version is supported by the workflow, which clears the staged notes and prepares the repository for the next development cycle automatically.

Does rust-srec release automation support bilingual English and Chinese release notes?

Bilingual English and Chinese release notes are supported during the promotion phase, where the workflow migrates unreleased notes into localized versioned pages and updates both language indexes.

What are the limitations of automating rust-srec versioning and release notes?

Automation for rust-srec versioning specifically targets maintainer workflows for cutting new versions, modifying Cargo.toml workspace versions, and organizing release notes, and may not cover custom publishing pipelines.