release-workflow

Automate version bumps, validation gates, and crates.io publishing for Hook packages.

2|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/heyAyushh/hook --skill release-workflow-heyayushh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-workflow
Source: https://github.com/heyAyushh/hook/tree/main/skills/release-workflow
Command: npx skills add https://github.com/heyAyushh/hook --skill release-workflow-heyayushh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing Hook involves coordinating version bumps, validation gates, binary releases, and crates.io publishing across multiple workspace members. This Skill consolidates the end-to-end process to reduce human error and ensure consistent, auditable releases.

Core Features & Use Cases

  • Version alignment: Keeps workspace members in sync when bumping the version across Cargo.toml files.
  • Validated release path: Enforces a local validation gate, ensuring checks pass before tagging.
  • Ordered publishing: Publishes binaries and crates in the required sequence to crates.io and GitHub Releases.
  • Troubleshooting & rollback: Provides steps to diagnose publish failures and perform rollbacks if needed.

Quick Start

Run the release workflow with the prepared version bumps and staged checks to publish a new tag.

Frequently Asked Questions about release-workflow

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

FAQPage Schema
How do I automate version bumping across a Rust workspace before publishing?

Automating version bumping across a Rust workspace involves keeping all Cargo.toml files in sync when applying a new version. This release workflow enforces consistent version alignment across workspace members to reduce human error before tagging.

What's the best way to enforce validation gates before creating a tag-based binary release?

Enforcing validation gates before a tag-based binary release requires running local checks successfully before tagging. This workflow automates that validated release path to ensure all validation gates pass prior to tagging binary releases.

How do I publish multiple workspace crates to crates.io in the correct sequence?

Publishing multiple workspace crates to crates.io requires an ordered sequence to prevent dependency failures. This workflow automates ordered publishing, ensuring binaries and crates are published in the required sequence to crates.io and GitHub Releases.

Can I perform a dry-run validation before publishing to crates.io?

Yes, you can perform a dry-run validation before publishing to crates.io. The release workflow includes built-in dry-run validation, allowing you to validate the entire end-to-end release process without making actual changes.

How do I troubleshoot and roll back a failed crates.io publishing step?

Troubleshooting and rolling back a failed crates.io publishing step involves diagnosing the specific publish failure. The workflow provides built-in steps to diagnose publish failures and perform rollbacks if the release process fails.