publish-extension

Coordinate multi-channel releases for the Cline VS Code extension.

65.9k|7.1k|Updated Jul 6, 2024
One-click install
npx skills add https://github.com/cline/cline --skill publish-extension
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-extension
Source: https://github.com/cline/cline/tree/main/.cline/skills/publish-extension
Command: npx skills add https://github.com/cline/cline --skill publish-extension

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill manages the complex, multi-channel release lifecycle of the Cline VS Code extension, ensuring version monotonicity, environment-gated deployments, and safe A/B rollout coordination.

Core Features & Use Cases

  • Multi-Channel Release Management: Handles stable, nightly, and legacy hotfix publishing workflows with automated version validation.
  • Rollout Coordination: Manages the PostHog-based A/B bundle rollout, allowing for safe feature flag dialing and empirical verification of user cohorts.
  • Automated Verification: Integrates pre-flight checks, test suite gating, and post-publish verification to prevent marketplace errors and broken builds.

Quick Start

Use the publish-extension skill to initiate a stable release for version 4.2.0 by dispatching the ab-package workflow with the appropriate branch references.

Frequently Asked Questions about publish-extension

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

FAQPage Schema
How do I automate VS Code extension deployment across multiple release channels?

VS Code extension deployment across multiple channels is orchestrated by coordinating stable, nightly, and legacy hotfix workflows with automated version validation. This ensures consistent versioning and prevents release conflicts across distribution environments.

What is marketplace version monotonicity and why does it matter for CI/CD rollouts?

Marketplace version monotonicity enforces strictly ascending release numbers to prevent downgrade errors during CI/CD rollouts. It is maintained through automated pre-flight validation checks that verify version sequencing before any production deployment occurs.

How can I safely roll out A/B bundle variants for a VS Code extension?

A/B bundle rollout variants are safely managed by coordinating PostHog-based feature flags during the extension release process. This allows empirical verification of user cohorts and controlled dialing of next-generation extension features.

Does this release coordination process handle environment approvals and pre-flight checks?

Release coordination explicitly handles environment approvals and integrates automated pre-flight checks with test suite gating. This prevents broken builds and marketplace errors by validating extension variants before production publishing.

What's the best way to publish a stable VS Code extension release without breaking existing builds?

Publishing a stable extension release without breaking builds is best achieved by dispatching the ab-package workflow with correct branch references. This triggers post-publish verification and strict monotonicity enforcement for safe deployment.