release-guardian-sdk-packages

Versions, validates, and publishes Guardian Rust crates and npm packages for coordinated SDK releases.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/hduoc2003/leviathan-guardian --skill release-guardian-sdk-packages-hduoc2003
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-guardian-sdk-packages
Source: https://github.com/hduoc2003/leviathan-guardian/tree/main/.agents/skills/release-guardian-sdk-packages
Command: npx skills add https://github.com/hduoc2003/leviathan-guardian --skill release-guardian-sdk-packages-hduoc2003

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating a release across four Rust crates and four npm packages requires updating many manifests and lockfiles, running the right tests and dry-runs, and following strict publish ordering—manual execution is error-prone and risks publishing out of dependency order or from the wrong branch. ## Core Features & Use Cases - Coordinated Version Bumping: Updates the workspace Cargo.toml, internal crate dependency versions, package.json files, and refreshes npm lockfiles to keep all publishable packages on one version line. - Validation and Dry-Runs: Runs targeted cargo tests, npm builds, README surface checks, and cargo/npm publish dry-runs before any irreversible step. - Safe Publish Handoff: Prepares the exact GitHub workflow dispatch (OIDC trusted publishing), npm publish commands in dependency order, and GitHub Release commands, stopping before irreversible actions unless explicitly approved. - Use Case: A maintainer wants to ship SDK version 0.16.1. The Skill inspects current versions, bumps all manifests and lockfiles, runs tests and dry-runs, then hands back copy-pasteable commands for the workflow dispatch, npm publish sequence, and draft GitHub Release. ## Quick Start Use the release-guardian-sdk-packages skill to prepare a coordinated release of the Guardian SDK crates and npm packages at version 0.16.1.

Frequently Asked Questions about release-guardian-sdk-packages

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

FAQPage Schema
How do I publish Rust crates and npm packages in one coordinated release?▼

Bump the workspace Cargo.toml version, internal crate dependency versions, and all package.json versions to the same target, then refresh npm lockfiles. Run cargo and npm publish dry-runs, then publish Rust crates via the publish-crates.yml GitHub workflow and npm packages in dependency order.

How do I publish Rust crates to crates.io with GitHub Actions trusted publishing?▼

Configure one crates.io trusted-publisher entry per crate bound to the repository, workflow file, and release environment. Dispatch the workflow with dry-run first, then run the real publish which uses OIDC authentication with no long-lived registry tokens.

What order should npm packages with internal dependencies be published?▼

Publish in dependency order so dependents can resolve their internal dependencies from the registry. Here the order is guardian-client, guardian-evm-client, miden-multisig-client (which depends on guardian-client), then guardian-operator-client.

Does cargo publish need a local crates.io token for this workflow?▼

No. Normal Rust publication runs through the publish-crates.yml GitHub workflow using OIDC trusted publishing, so maintainers should not run cargo publish locally or use cargo login. The workflow fails closed if trusted publishing fails.

Why does a draft GitHub Release not trigger the Docker publish workflow?▼

Draft releases do not fire the release: published event, so downstream workflows like Docker Publish stay idle. Publishing the draft triggers the Rust crates, npm packages, and Docker Publish workflows, with Docker waiting for release-environment approval.