Check release readiness and trigger the release pipeline for Azure SDK packages. **UTILITY SKILL**. USE FOR: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK". DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation. INVOKES: azure-sdk-mcp:azsdk_release_sdk.
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Check release readiness and trigger the release pipeline for Azure SDK packages. **UTILITY SKILL**. USE FOR: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK". DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation. INVOKES: azure-sdk-mcp:azsdk_release_sdk.
compatibility
azure-sdk-mcp server, SDK package merged on release branch. Supports .NET, Java, JavaScript, Python, Go
SDK Release
MCP Tools
Tool
Purpose
azure-sdk-mcp:azsdk_release_sdk
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).
Determine Intent — If the user explicitly asks to "check readiness" or "check if ready", run azure-sdk-mcp:azsdk_release_sdk with checkReady: true. Otherwise, proceed to trigger the release directly.
Trigger Release — Run azure-sdk-mcp:azsdk_release_sdk with checkReady: false (the default). Show pipeline link and inform user they must approve the release stage.
Review Results — If the release fails due to readiness issues, display failing checks and guide user to resolve.
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.
