azsdk-common-sdk-release

Checks release readiness and triggers the Azure SDK release pipeline for prepared packages.

2.6k|2.2k|Updated Dec 6, 2011
One-click install
npx skills add https://github.com/Azure/azure-sdk-for-java --skill azsdk-common-sdk-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azsdk-common-sdk-release
Source: https://github.com/Azure/azure-sdk-for-java/tree/main/.github/skills/azsdk-common-sdk-release
Command: npx skills add https://github.com/Azure/azure-sdk-for-java --skill azsdk-common-sdk-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing an Azure SDK package requires verifying readiness prerequisites and manually triggering the release pipeline, which is error-prone when done by hand. This Skill automates readiness checks and pipeline triggering through the azure-sdk-mcp server, guiding you through validation and approval steps.

Core Features & Use Cases

  • Release Readiness Check: Validates that a package meets all release prerequisites before attempting to publish, surfacing failing checks for resolution.
  • Release Pipeline Triggering: Launches the Azure SDK release pipeline for a given package and language, returning the pipeline link and reminding you of the required approval stage.
  • Multi-Language Support: Works with .NET, Java, JavaScript, Python, and Go SDK packages already merged on a release branch.
  • Use Case: You have merged azure-messaging-eventhubs for Java and want to ship it. Ask the Skill to check readiness, review any failing prerequisites, then trigger the release and approve the release stage in the pipeline.

Quick Start

Ask the assistant to check if your Azure SDK package is ready for release and trigger the release pipeline by providing the package name and language.

Frequently Asked Questions about azsdk-common-sdk-release

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

FAQPage Schema
How do I trigger an Azure SDK release pipeline?

Provide the package name and language, and the Skill invokes the azure-sdk-mcp azsdk_release_sdk tool with checkReady set to false. It returns the pipeline link, and you must manually approve the release stage to complete publishing.

How do I check if my Azure SDK package is ready for release?

Ask to check release readiness with your package name and language. The Skill runs azsdk_release_sdk with checkReady set to true and displays each prerequisite check, highlighting any failures you need to resolve first.

Which languages does the Azure SDK release workflow support?

The release workflow supports .NET, Java, JavaScript, Python, and Go SDK packages. The package must already be prepared and merged on a release branch before readiness checks or pipeline triggering can run.

Can I trigger an SDK release without the azure-sdk-mcp server?

No, the azure-sdk-mcp server is required and there is no CLI fallback for the release workflow. If the server is unavailable, you must configure the MCP connection before running readiness checks or triggering releases.

What happens if the release readiness check fails?

The Skill displays each failing prerequisite check individually so you can resolve them one at a time. After fixing the issues, you can re-run the readiness check before attempting to trigger the release again.

When should I not use the SDK release skill?

Do not use it for SDK development, code generation, pipeline debugging, or release plan creation. It only handles readiness verification and pipeline triggering for packages already prepared for release.