release-zakura

Manage Zakura Zcash node release lifecycle with versioning and changelog generation.

42|10|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/zakura-core/zakura --skill release-zakura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-zakura
Source: https://github.com/zakura-core/zakura/tree/main/.agents/skills/release-zakura
Command: npx skills add https://github.com/zakura-core/zakura --skill release-zakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill manages the complex, multi-step process of preparing, validating, and publishing Zakura node releases, ensuring that versioning, dependency graphs, and security protocols are strictly followed.

Core Features & Use Cases

  • Release Preparation: Automates the mechanical aspects of version bumping, changelog assembly, and release branch creation.
  • Validation & Compliance: Executes rigorous checks on crate publish graphs, packaging integrity, and security policy adherence.
  • Use Case: When preparing a new release candidate, use this Skill to verify that all changed crates are correctly versioned and that the release branch meets all safety requirements before dispatching the final build workflow.

Quick Start

Use the release-zakura skill to prepare the release branch for version v1.0.0-rc5 and validate the crate publish graph.

Frequently Asked Questions about release-zakura

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

FAQPage Schema
How do I automate Rust crate publishing and versioning for a Zcash full node release?

Automate Rust crate publishing and versioning by managing the end-to-end release lifecycle, executing version bumping, changelog generation, and crate publishing while verifying package integrity via Cargo and local shell scripts.

What is the process for validating a crate publish graph before a stable release?

Validating a crate publish graph involves executing rigorous checks on dependency graphs, packaging integrity, and security policy adherence to ensure all changed crates are correctly versioned before dispatching the build workflow.

Does this release automation workflow integrate with GitHub Actions and Cargo?

Yes, release automation requires integration with GitHub Actions, Cargo, and local shell scripts to verify package integrity, enforce tag protection, and automate the deployment pipeline for Zcash node releases.

How do I prepare a release candidate branch and ensure compliance with security policies?

Prepare a release candidate branch by automating version bumping and branch creation, then run compliance checks to verify the branch meets tag protection rules and security policy requirements before final validation.

Can I verify dependency graphs and package integrity for Rust crates locally before publishing?

Verify dependency graphs and package integrity locally using integrated Cargo commands and shell scripts that execute rigorous checks on crate publish graphs and security policy adherence before publishing.

What are the limitations when automating release engineering workflows for stable versions versus release candidates?

Limitations include strict adherence to tag protection and security policies; release candidates require full validation of changed crate versions and branch safety requirements before dispatching the final build workflow for stable versions.