| name | fluid-release |
| description | Guide the Fluid Framework client release group through minor releases, patch releases, and post-release type test updates. Use when performing a release, preparing for a release, creating release branches, bumping versions, generating changelogs/release notes, or updating type test baselines after a release. Triggers on mentions of release, releasing, release branch, version bump, release notes, changelog generation, patch release, minor release, or release engineering. |
Fluid Framework Client Release
Release workflow for the client release group. Supports two modes: interactive (default) and autonomous.
Mode Selection
At the start of every release session, ask the user:
Would you like to run in interactive or autonomous mode?
Interactive Mode (default)
Run commands autonomously but pause before creating PRs, pushing branches, or triggering builds. Ask for version confirmation at key points. This is the current behavior.
Autonomous Mode
Run the entire selected phase end-to-end without pausing. Requirements:
- Version info upfront: The user must provide all version numbers before starting (current release version and/or next version, depending on phase). Do not prompt for versions mid-flow.
- No confirmation pauses: Create PRs, push branches, and run
flub release without asking. Include clear commit messages and PR descriptions.
- Phase-scoped execution: Each phase runs to completion, then reports what the user needs to do next (e.g., "queue the ADO build" or "wait for npm feeds, then re-invoke for type test updates").
If the user provides version info in their initial message (e.g., "release 2.90.0 autonomously"), skip the version questions entirely.
Workflow Selection
Ask the user which phase they need (or detect from context in autonomous mode):
