promote-release

Promote releases across downstream Units with preflight checks and atomic ChangeSets.

2|2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/confighub/confighub-skills --skill promote-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: promote-release
Source: https://github.com/confighub/confighub-skills/tree/main/skills/promote-release
Command: npx skills add https://github.com/confighub/confighub-skills --skill promote-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to plan, validate, and execute fleet-wide release promotions across environment spaces by wrapping changes in ChangeSets, coordinating downstream updates, and providing rollback and approval paths.

Core Features & Use Cases

  • Preflight readiness checks across source and destination env-spaces to determine scope, blockers, and diffs.
  • ChangeSet orchestration: create, apply, and close a grouped set of unit upgrades with atomic rollback guarantees.
  • Bulk promotion workflow: upgrade all in-scope downstream Units in a single, auditable operation and hand off to cub-apply for runtime rollout.

Quick Start

Promote an app from one env-space to the next by running preflight checks, creating a ChangeSet, bulk-upgrading downstream Units, then closing the ChangeSet and handing off to cub-apply.

Frequently Asked Questions about promote-release

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

FAQPage Schema
How do I promote a release from staging to prod safely?

Release promotion from staging to prod is handled by running preflight readiness checks, creating an atomic ChangeSet, and bulk-upgrading downstream Units before closing the ChangeSet to ensure a safe, coordinated rollout.

What is an atomic ChangeSet and how does it work for fleet-wide upgrades?

An atomic ChangeSet groups multiple Unit upgrades into a single auditable operation, ensuring that all downstream changes apply together or roll back together, providing safe fleet-wide release coordination.

Can I roll back a bulk promotion if the preflight checks pass but the deployment fails?

Yes, rollback is supported via rollback-revision, providing a defined path to revert a completed ChangeSet if downstream Unit upgrades encounter issues during the runtime rollout handoff to cub-apply.

How do I coordinate upgrades across many downstream Units in a single operation?

You can execute a bulk promotion workflow that upgrades all in-scope downstream Units in one coordinated operation, wrapping the updates in a ChangeSet and handing off to cub-apply for runtime rollout.

Does the promotion workflow require an approval process before applying changes to production?

Yes, an approval workflow can be enforced when required, adding a gate before ChangeSets are applied to downstream Units in production env-spaces to ensure changes are reviewed.

What are the limitations of promoting releases without preflight gates?

Without preflight gates, you lose scope analysis, blocker detection, and environment diff checks between source and destination env-spaces, risking unvalidated or conflicting Unit upgrades during fleet-wide rollouts.