Check release readiness and/or trigger the release pipeline
Steps
Collect Info — Get packageName and language from the user. Optionally get branch (defaults to main).
Check Readiness — Run azure-sdk-mcp:azsdk_release_sdk with checkReady: true to verify API review approval, changelog, package name approval, and release date.
Review Results — If not ready, display failing checks and guide user to resolve.
Trigger Release — Once ready, run azure-sdk-mcp:azsdk_release_sdk with checkReady: false. Show pipeline link and inform user they must approve the release stage.
Examples
"Check if azure-storage-blob is ready for release"
"Trigger release for @azure/core-rest-pipeline on JavaScript"
Troubleshooting
If readiness check fails, review each failing prerequisite individually before re-triggering.
Requires azure-sdk-mcp server. No CLI fallback — prompt user to configure MCP if unavailable.