skills.rest
mrsekut
mrsekutCOMMUNITY
Explore all skills by this author →
Website𝕏@mrsekutGitHub

release

Automate Rust and Nix release workflows from version bumps to crates.io publishing.

Updated Mar 23, 2026
Search Tags:#automation#git#versioning#release#nix#cargo#crates.io
One-click install
npx skills add https://github.com/mrsekut/strand --skill release-mrsekut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/mrsekut/strand/tree/main/.claude/skills/release
Command: npx skills add https://github.com/mrsekut/strand --skill release-mrsekut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release processes for Rust and Nix projects are tedious and error-prone, and this Skill automates the full lifecycle from version bumps to publishing and pushing.

Core Features & Use Cases

  • Automates bumping versions in Cargo.toml and flake.nix to ensure consistent releases.
  • Builds and regenerates lockfiles to align artifacts with the new version.
  • Publishes packages to crates.io and pushes Git tags, providing a complete release record.

Quick Start

Provide the new version to start the full release workflow.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Rust and Nix release workflows from version bump to publishing?▼

Automating Rust and Nix release workflows involves sequentially bumping versions in Cargo.toml and flake.nix, building artifacts, publishing to crates.io, and pushing Git tags. This enforces semver validation and safe push guardrails.

What is the best way to keep Cargo.toml and flake.nix versions consistent during a release?▼

Keeping Cargo.toml and flake.nix versions consistent requires applying automated version bumps across both files simultaneously. This ensures aligned artifacts by regenerating lockfiles and validating semver before proceeding with the release.

Does this release automation enforce semver validation before pushing Git tags?▼

Yes, release automation enforces semver validation before pushing Git tags or publishing. It applies sequential task execution and safe push guardrails to prevent invalid version increments from reaching your repository or crates.io.

How do I publish a Rust package to crates.io after updating the version in Cargo.toml?▼

Publishing a Rust package to crates.io after a Cargo.toml version update requires building the project, regenerating lockfiles, and executing the publish command. Sequential task execution ensures the package is published only after successful validation.

Can I use this for a Nix project that needs lockfile regeneration and Git tagging?▼

Yes, you can use this for Nix projects requiring lockfile regeneration and Git tagging. It automates the end-to-end release workflow, aligning flake.nix versions with rebuilt artifacts and pushing a complete Git release record.

Why do my Rust and Nix releases fail due to misaligned lockfiles and versions?▼

Rust and Nix releases fail due to misaligned lockfiles when versions are bumped manually without rebuilding. Automating the release workflow regenerates lockfiles and applies version bumps concurrently to ensure artifact alignment and prevent errors.

Related Skills

Explore More Software Engineering Skills→
rust-worksrust-works
10

release

Automate Rust project releases with version bumps, changelog updates, and publishing.

Official
Advanced
Otard95Otard95

github-ci-architecture

Explain GitHub Actions CI/CD architectural decisions and configuration rationale.

Community
Intermediate
liauw-medialiauw-media
3

pre-commit-hooks

Configure pre-commit hooks for JavaScript/TypeScript, Python, and PHP projects.

Community
Advanced
bobmatnycbobmatnyc
15

cargo-publish

Automates validated publishing of Rust crates to crates.io with dependency ordering and git checks.

Community
Advanced