releasing

Coordinates versioned releases across stable and nightly channels with enforced tagging and audit trails.

158|12|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/nteract/nteract --skill releasing-nteract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: releasing
Source: https://github.com/nteract/nteract/tree/main/.agents/skills/releasing
Command: npx skills add https://github.com/nteract/nteract --skill releasing-nteract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release and version governance for a multi-artifact project, ensuring consistent tagging and strict manual control over deployment.

Core Features & Use Cases

  • Version stamping rules for desktop app, runtimes, CLI, and Python bindings.
  • Coordinated bumping and publishing workflows across stable and nightly release channels.
  • Governance and audit trails for release tagging, artifact alignment, and cross-component synchronization.

Quick Start

Initiate a manual release run to bump the base version and publish all artifacts.

Frequently Asked Questions about releasing

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

FAQPage Schema
How do I coordinate versioned releases across multiple artifacts?

Coordinated versioned releases use guardrail-driven workflows to stamp versions consistently across desktop apps, runtimes, CLIs, and Python bindings. This ensures strict cross-component synchronization and aligned CI/CD steps for all artifacts.

What is the best way to manage stable and nightly release channels for a project?

Managing stable and nightly release channels requires guardrail-driven workflows that apply specific bump rules to each channel. This aligns CI/CD steps and publishes artifacts appropriately based on the targeted release type.

How does version stamping work for CI/CD deployment pipelines?

Version stamping in CI/CD pipelines applies defined bump rules to stamp versions consistently. The guardrail-driven workflow tags releases and aligns deployment steps across components to enforce strict manual control over the release process.

Does this release governance workflow support multi-artifact projects?

Yes, this release governance workflow supports multi-artifact projects. It coordinates version bumping and publishing workflows across components, providing audit trails for artifact alignment and cross-component synchronization.

Can I use manual control to enforce strict deployment governance?

Yes, you can enforce strict manual control over deployment by initiating a manual release run. This triggers the guardrail-driven workflow to bump the base version, tag the release, and publish all artifacts consistently.