release-workflow

Release workflows track progression through build promotion phases, candidate builds, and gate checks. Query the current release state to see which promoted and candidate builds are active, what tests have passed, and which gates remain before the next phase.

Candidate builds are staging versions undergoing test and validation; promoted builds have cleared gate checks and advanced in the release lifecycle. The workflow orchestrates async tasks to move candidates through gates and into promotion status.

Gate checks are checkpoints that validate build readiness before promotion. They evaluate test results and state conditions; MCP commands execute gate logic and advance or hold builds based on success or failure criteria.

Yes. Release workflows coordinate parallel async task orchestration and MCP-based command execution to automate sequencing across the build promotion lifecycle, reducing manual intervention and enforcing consistent gate logic.

You need visibility into the complete release task graph structure, which shows dependencies between promotion stages, test phases, and gate checks. The workflow outlines sequencing, parallel tasks, and how each checkpoint blocks or enables downstream actions.