Menu
Automate bumping typespec-python version in emitter-package.json for the Azure SDK for Python repository. Use this skill when the user wants to update @azure-tools/typespec-python to the latest version, create a PR for the version bump, or manage emitter-package.json updates.
| name | emitter-package-update |
| description | Automate bumping typespec-python version in emitter-package.json for the Azure SDK for Python repository. Use this skill when the user wants to update @azure-tools/typespec-python to the latest version, create a PR for the version bump, or manage emitter-package.json updates. |
Bump @azure-tools/typespec-python to the latest version in emitter-package.json and create a PR.
The Python emitter ecosystem consists of two packages:
@azure-tools/typespec-python): Lives in Azure/typespec-azure. This is the emitter used for Azure SDK generation.@typespec/http-client-python): Lives in microsoft/typespec. The branded emitter wraps this package.When eng/emitter-package.json is updated on main, the TypeSpec Python Regenerate Tests workflow triggers automatically and pushes regenerated test code to the typespec-python-generated-tests branch.
Before running this workflow, verify the following tools are installed:
# Check npm-check-updates
npx npm-check-updates --version
# Check tsp-client
tsp-client --version
# Check GitHub CLI
gh --version
If any tool is missing:
npm install -g npm-check-updatesnpm install -g @azure-tools/typespec-client-generator-cliwinget install GitHub.cliReset and sync the SDK repo to a clean state:
git reset HEAD && git checkout . && git clean -fd && git checkout origin/main && git pull origin main
Run npm-check-updates to find the latest @azure-tools/typespec-python version:
npx npm-check-updates --packageFile eng/emitter-package.json
Extract the target version from the output (e.g., 0.61.3).
git checkout -b bump-typespec-python-{version}
Replace {version} with the actual version number (e.g., bump-typespec-python-0.61.3).
Apply the version update:
npx npm-check-updates --packageFile eng/emitter-package.json -u
Align @azure-tools/openai-typespec and @typespec/openapi3 with the versions pinned in azure-rest-api-specs/package.json to ensure consistency between the emitter and the spec repo. Check the spec repo's versions and update eng/emitter-package.json accordingly (e.g., set "@azure-tools/openai-typespec": "1.8.0" and "@typespec/openapi3": "1.9.0" to match).
If you have a local clone of typespec-azure, regenerate the lock file using the branded emitter's package.json to ensure devDependencies are aligned:
tsp-client generate-config-files \
--package-json=<path-to-local-typespec-azure>/packages/typespec-python/package.json
Otherwise, regenerate the lock file only:
tsp-client generate-lock-file
git add eng/emitter-package.json eng/emitter-package-lock.json
git commit -m "bump typespec-python {version}"
Push branch and create PR:
git push -u origin bump-typespec-python-{version}
gh pr create --title "bump typespec-python {version}" --body "Bump @azure-tools/typespec-python to version {version}"
Once the PR merges to main, the TypeSpec Python Regenerate Tests workflow triggers automatically because eng/emitter-package.json was modified. It will:
eng/emitter-package.jsontypespec-python-generated-tests branchInteractive wizard that walks service teams through creating a package-specific skill for their Azure SDK package. Scans the package, detects customization patterns, scaffolds a SKILL.md with references, and validates with vally lint. The skill is placed inside the package's .github/skills/ directory so find-package-skill discovers it automatically. WHEN: create package skill; add service skill; bootstrap skill for package; new package skill; skill for my SDK package; write skill for search; write skill for cosmos.
**UTILITY SKILL** — Must be consulted before making any changes to packages under sdk/. Discovers and loads package-specific domain knowledge that prevents common mistakes. WHEN: "add feature to package", "fix bug in package", "modify package code", "regenerate from typespec", "change client library".
Create, get, update, abandon, and link SDK PRs to release plan work items for Azure SDK releases. **UTILITY SKILL**. USE FOR: "create release plan", "get release plan", "update release plan", "update API spec in release plan", "update SDK details in release plan", "abandon release plan", "link SDK PR to plan", "namespace approval", "check release plan status". DO NOT USE FOR: SDK code generation, pipeline troubleshooting, API review feedback. INVOKES: azure-sdk-mcp:azsdk_create_release_plan, azure-sdk-mcp:azsdk_get_release_plan, azure-sdk-mcp:azsdk_get_release_plan_for_spec_pr, azure-sdk-mcp:azsdk_update_release_plan, azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan, azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan, azure-sdk-mcp:azsdk_abandon_release_plan, azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan, azure-sdk-mcp:azsdk_link_namespace_approval_issue.
Create a GitHub PR for API review by comparing a baseline API surface against a target tag or branch. Use this when the user wants to create an API review PR, compare API changes between versions, or review API surface differences for a package.
Generate an API markdown file and token file using ApiView. Use this when the user wants to generate an API markdown file and review API changes.
Analyze and resolve APIView review feedback on Azure SDK PRs. **UTILITY SKILL**. USE FOR: APIView comments, API review feedback, SDK API surface changes. DO NOT USE FOR: general code review, non-APIView feedback. INVOKES: azure-sdk-mcp:azsdk_apiview_get_comments, azure-sdk-mcp:azsdk_customized_code_update, azure-sdk-mcp:azsdk_typespec_delegate_apiview_feedback, azure-sdk-mcp:azsdk_run_typespec_validation, azure-sdk-mcp:azsdk_package_generate_code.