release

Automate Rust release workflows with Cargo, GitHub, and CI.

1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/langston-barrett/lun --skill release-langston-barrett
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/langston-barrett/lun/tree/main/.claude/skills/release
Command: npx skills add https://github.com/langston-barrett/lun --skill release-langston-barrett

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Cut and publish a release by coordinating changelog prep, version bumps, pull requests, CI checks, tagging, and publishing.

Core Features & Use Cases

  • Automates version bumps and changelog updates for Rust projects using Cargo.
  • Creates and pushes a release PR, triggers CI, and tags the release.
  • Publishes a GitHub release after CI success and updates project files accordingly.

Quick Start

Run the release automation to bump the version, update CHANGELOG, open a PR, and publish the 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 release workflows with Cargo and GitHub?

Automate Rust release workflows by coordinating Cargo version bumps, CHANGELOG.md updates, pull request creation, CI validation, and GitHub release publishing across branches.

How do I generate changelog entries and bump versions for a Cargo project?

Generate changelog entries and bump versions by executing the release automation scripts that update CHANGELOG.md and Cargo project files, then orchestrate the changes through a release PR to trigger CI validation.

Can I use this release automation for non-Rust projects or projects without a CHANGELOG.md?

This release automation is designed specifically for Cargo-based Rust projects with a CHANGELOG.md and GitHub integration, so it does not apply to non-Rust projects or repositories lacking these specific file requirements.

Does the release workflow trigger GitHub releases automatically after CI succeeds?

Yes, the workflow triggers GitHub release publishing automatically after CI checks succeed, handling the tagging and project file updates to ensure the release is published only when validation passes.

Do I need the GitHub CLI installed to automate release PRs and publishing?

Yes, you need the GitHub CLI installed locally, because the release workflow relies on it for Git operations, GitHub integration, pull request creation, and release publishing interactions.

What is the best way to coordinate CI validation and tagging during a Rust release?

Coordinate CI validation and tagging by using an automated release workflow that creates a release PR, waits for CI success, and then tags the release and publishes it to GitHub, ensuring validation completes before publishing.