release-management

Automate end-to-end software releases across crates.io, npm, and docs.

4|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/d-o-hub/chaotic_semantic_memory --skill release-management-d-o-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-management
Source: https://github.com/d-o-hub/chaotic_semantic_memory/tree/main/.agents/skills/release-management
Command: npx skills add https://github.com/d-o-hub/chaotic_semantic_memory --skill release-management-d-o-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Centralizes and automates the end-to-end software release process across crates.io, npm, and documentation deployments, reducing manual toil and release errors.

Core Features & Use Cases

  • Version synchronization across Cargo.toml, CHANGELOG.md, and package manifests to keep all artifacts in sync.
  • Trusted publishing through GitHub Actions using OIDC to publish to crates.io and npm without long-lived tokens.
  • Automated release notes, tagging, and docs deployment to GitHub Pages.
  • Use Case: Before releasing a new version, run the validation script, then execute the release pipeline to publish artifacts and update docs.

Quick Start

Run the pre-release validation script and follow the release script to tag, publish, and deploy the release.

Frequently Asked Questions about release-management

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

FAQPage Schema
How do I automate releases across crates.io, npm, and docs in a single pipeline?

Automate multi-repo software releases across crates.io, npm, and docs using a unified pipeline that handles version syncing, trusted publishing via OIDC, and automated tagging. It centralizes the end-to-end process to reduce manual toil and release errors.

How does trusted publishing to npm and crates.io work without long-lived tokens?

Trusted publishing to npm and crates.io uses GitHub Actions with OIDC authentication to establish trust without long-lived tokens. This mechanism securely authorizes the release pipeline to publish artifacts directly from your continuous integration environment.

What's the best way to keep version numbers synchronized across Cargo.toml, package manifests, and CHANGELOG.md?

Version synchronization across Cargo.toml, package manifests, and CHANGELOG.md is handled automatically by the release pipeline. It updates all configured artifacts simultaneously during the release process to ensure all project files remain in sync.

How do I validate a multi-repo project before running the release pipeline?

Validate a multi-repo project by running the pre-release validation script before executing the release pipeline. This process checks your project readiness, after which the release script tags, publishes, and deploys the release automatically.

Does this release automation handle deployment to GitHub Pages and release notes generation?

Release automation handles deployment to GitHub Pages and generates release notes automatically. After executing the release pipeline, the process applies automated tagging, publishes artifacts, and updates documentation deployments seamlessly.