release

Automate Cargo/Rust release workflows with tests, version bumps, and tag creation.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/dawsonblock/OracleOS --skill release-dawsonblock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/dawsonblock/OracleOS/tree/main/Interface/Web/worktrunk-main/.claude/skills/release
Command: npx skills add https://github.com/dawsonblock/OracleOS --skill release-dawsonblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates and standardizes the release workflow for software projects, reducing manual toil, ensuring consistent versioning, changelog updates, and deterministic release steps.

Core Features & Use Cases

  • Automated release pipeline: orchestrates tests, version bumps, changelog updates, commits, and tag creation to produce reliable releases.
  • Contributor credits and change visibility: surfaces external PR authors and issue reporters for attribution during the release process.
  • Release promotion and documentation: handles Git tags and publishing procedures to crates.io and GitHub, with optional prompts for user confirmation on release type.
  • Use Case: When preparing a new software version, invoke the release workflow to validate changes, update docs, and publish to crates.io and GitHub.

Quick Start

Run the release workflow to bump the version, update the changelog, commit changes, and push tags to create a new release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Rust crate publishing to crates.io and GitHub releases?

Automating Rust crate publishing involves coordinating pre-release tests, Cargo version bumps, changelog updates, and Git tag creation. This standardizes the process to ensure deterministic release steps and reliable deployments to crates.io.

What is the best way to update a changelog and bump versions before publishing a Rust crate?

Updating a changelog and bumping versions is best handled by an automated release pipeline that modifies Cargo configurations, generates change visibility logs, and commits the changes. This reduces manual toil and ensures consistent versioning across releases.

Can I include contributor credits and external PR authors in my automated GitHub release workflow?

Yes, you can include contributor credits in your GitHub release workflow. The release process surfaces external PR authors and issue reporters during the version bump and tagging phases to provide proper attribution in your changelog.

Does this release automation workflow support optional confirmation prompts before pushing Git tags to crates.io?

Yes, the release automation workflow supports optional confirmation prompts. It can pause during the release pipeline to ask for user confirmation on the release type before proceeding with Git tag creation and crates.io publishing.

How do I run pre-release checks and validate changes before publishing a new software version to crates.io?

Running pre-release checks requires orchestrating tests across your Cargo project before applying version bumps. The release workflow validates changes, updates documentation, and ensures all checks pass before final tagging and pushing.