publish

Automate versioning, tagging, and release workflows for Rust binaries and VSCode extensions.

28|3|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Minara-AI/cc-connect --skill publish-minara-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/Minara-AI/cc-connect/tree/main/.claude/skills/publish
Command: npx skills add https://github.com/Minara-AI/cc-connect --skill publish-minara-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill manages the complex, multi-artifact release process for cc-connect, ensuring that Rust binaries and the VSCode extension are tagged, built, and deployed in the correct order to prevent dependency mismatches.

Core Features & Use Cases

  • Artifact Coordination: Handles independent release cadences for Rust binaries and the VSCode extension.
  • Dependency Management: Enforces correct release ordering when changes affect both the CLI tools and the editor extension.
  • Use Case: When a new feature requires both a CLI update and a UI change in the VSCode extension, this Skill guides you through tagging the Rust release first, verifying the build, and then releasing the extension.

Quick Start

Ask the AI to publish a new version of the Rust binaries and the VSCode extension by providing the desired version number and a summary of the changes.

Frequently Asked Questions about publish

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

FAQPage Schema
How do I automate versioning and release for a Rust binary and VSCode extension?

Automating versioning and release involves coordinating tags and CI/CD triggers to build and deploy multi-platform artifacts. This Skill manages the correct release ordering for Rust binaries and VSCode extensions to prevent cross-artifact dependency mismatches.

Why does the VSCode extension release fail after updating the Rust CLI binary?

The release may fail due to cross-artifact dependency mismatches. When features require both a CLI update and a UI change, you must tag the Rust release first, verify the build, and then release the extension to enforce correct ordering.

Do I need GitHub CLI authentication to automate Rust and VSCode extension publishing?

Yes, GitHub CLI authentication is required for successful artifact distribution. The automated release workflow relies on it to manage tagging, trigger CI/CD pipelines, and deploy Rust binaries and VSCode extensions across multiple platforms.

What is the correct tag naming convention for releasing Rust binaries and VSCode extensions?

Tag naming conventions must be strictly followed for successful artifact distribution. The workflow enforces specific tag formats to correctly sequence Rust binary and VSCode extension releases, ensuring CI/CD pipelines trigger properly for multi-platform deployments.

Can I release a VSCode extension independently from the Rust binary using automation?

Yes, artifact coordination handles independent release cadences for Rust binaries and the VSCode extension. The workflow manages separate tagging while enforcing correct release ordering only when changes affect both the CLI tools and the editor extension.

What is the best way to coordinate multi-platform CI/CD deployments for Rust and VSCode?

The best way is to use an automated workflow that manages cross-artifact dependencies and CI/CD trigger logic. This ensures Rust binaries and VSCode extensions are tagged, built, and deployed in the correct order for multi-platform distribution.