http-client-python-bump-and-release

Stars5,811

Forks382

UpdatedFebruary 11, 2026 at 02:58

Create a PR to bump TypeSpec/Azure Tools dependencies, update peer dependencies, or release a new version of the http-client-python package.

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.

Source

microsoft

microsoft/typespec

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	http-client-python-bump-and-release
description	Create a PR to bump TypeSpec/Azure Tools dependencies, update peer dependencies, or release a new version of the http-client-python package.

HTTP Client Python Bump and Release

Create a PR to bump dependencies and release a new version of the http-client-python package.

Note: {REPO} refers to the root folder of the microsoft/typespec repository.

Prerequisites

Before starting, verify that npm-check-updates is available:

npx npm-check-updates --version

If the command fails or prompts for installation, install it globally:

npm install -g npm-check-updates

Workflow

Navigate to the package directory:
```
cd {REPO}/packages/http-client-python
```

Reset and sync with main:

git reset HEAD && git checkout . && git checkout origin/main && git pull origin main

Create release branch (use current date in MM-DD format):
```
git checkout -b publish/python-release-{MM-DD}
```

Update dependencies:

npx npm-check-updates -u --filter @typespec/*,@azure-tools/* --packageFile package.json

Update peerDependencies in package.json:
- If format is ">=0.a.b <1.0.0": Update only the 0.a.b portion, keep the range format unchanged
- If format is "^1.a.b": Update to the latest version
Verify devDependencies versions for specs:
- Check @typespec/http-specs and @azure-tools/azure-http-specs
- If the original version in package.json is newer than the updated value, keep the original version
- Dev versions are typically in the form x.y.z-alpha.N-dev.M (e.g., 0.1.0-alpha.37-dev.3).
Example:
- Original: @typespec/http-specs: 0.1.0-alpha.12-dev.5, updated by step 4 to 0.1.0-alpha.11 → keep 0.1.0-alpha.12-dev.5.
- Original: @typespec/http-specs: 0.1.0-alpha.12-dev.5, updated by step 4 to 0.1.0-alpha.12 → keep 0.1.0-alpha.12 (step 4 works as expected).
- Original: @azure-tools/azure-http-specs: 0.1.0-alpha.12-dev.2, updated to 0.1.0-alpha.11 → keep 0.1.0-alpha.12-dev.2.
- Original: @azure-tools/azure-http-specs: 0.1.0-alpha.12-dev.2, updated to 0.1.0-alpha.12 → keep 0.1.0-alpha.12 (step 4 works as expected).
Run version change script:
```
npm run change:version
```

Build and commit:

npm install && npm run build && git add -u && git commit -m "bump version"

Push and create PR:
```
cd {REPO}
git push origin HEAD
```
Create PR with title [python] release new version and no description.

More from this repository

same repository

generate-from-typespec

microsoft/typespec

Generate Python SDK code from a TypeSpec specification using the local emitter. Use this skill when the user wants to generate/regenerate a Python client from a TypeSpec spec, provides a GitHub URL or local path to a TypeSpec project, or says things like "generate from this spec", "emit Python from this tsp", "regenerate the SDK", or "compile this TypeSpec for Python".

2026-08-045.8k

csharp-spector-coverage-gaps

microsoft/typespec

Discovers and implements gaps in Spector test coverage for the C# HTTP client emitter. Use when asked to find missing Spector scenarios, add Spector test coverage, or implement a specific Spector spec for the C# emitter.

2026-07-215.8k

minimal-repro

microsoft/typespec

Help create a minimal reproduction for a TypeSpec compiler or emitter bug. Use when a user provides TypeSpec source (pasted code or a GitHub URL) and describes an issue. Reproduces locally and reduces to a single-file repro.

2026-06-015.8k

emitter-prep-for-pr

microsoft/typespec

Prepare language emitter changes for PR: validate (build, format, lint), add a changeset, and push. This skill is specifically for the language emitter packages (http-client-python, http-client-csharp, http-client-java) - NOT for core TypeSpec packages like compiler, http, openapi3, etc. Use when the user wants to finalize emitter changes, says things like "prep for pr", "prepare for PR", "validate and push", "add changeset", or "finalize changes".

2026-04-215.8k

writing-python-sdk-spector-mock-api-tests

microsoft/typespec

Writes TypeSpec http-client-python generator mock API tests (azure/unbranded/shared) from a Spector case. Use when given a Spector case link or a PR link that modifies Spector cases under http-specs/azure-http-specs.

2026-04-095.8k

diff-upstream

microsoft/typespec

Regenerate the local emitter and diff the generated code against the upstream baseline checked into autorest.python. Use this skill when the user wants to see how their emitter changes affect generated code compared to what's currently in production, says things like "diff upstream", "compare to baseline", "what changed vs production", "show me the diff", "how does this affect generated code", or wants to validate their changes produce the expected output differences.

2026-02-275.8k

HTTP Client Python Bump and Release

Create a PR to bump dependencies and release a new version of the http-client-python package.

Note: {REPO} refers to the root folder of the microsoft/typespec repository.

Prerequisites

Before starting, verify that npm-check-updates is available:

npx npm-check-updates --version

If the command fails or prompts for installation, install it globally:

npm install -g npm-check-updates

Workflow

Navigate to the package directory:

cd {REPO}/packages/http-client-python

Reset and sync with main:

git reset HEAD && git checkout . && git checkout origin/main && git pull origin main

Create release branch (use current date in MM-DD format):

git checkout -b publish/python-release-{MM-DD}

Update dependencies:

npx npm-check-updates -u --filter @typespec/*,@azure-tools/* --packageFile package.json

Update peerDependencies in package.json:

If format is ">=0.a.b <1.0.0": Update only the 0.a.b portion, keep the range format unchanged
If format is "^1.a.b": Update to the latest version

Verify devDependencies versions for specs:

Check @typespec/http-specs and @azure-tools/azure-http-specs
If the original version in package.json is newer than the updated value, keep the original version
Dev versions are typically in the form x.y.z-alpha.N-dev.M (e.g., 0.1.0-alpha.37-dev.3).

Example:

Original: @typespec/http-specs: 0.1.0-alpha.12-dev.5, updated by step 4 to 0.1.0-alpha.11 → keep 0.1.0-alpha.12-dev.5.
Original: @typespec/http-specs: 0.1.0-alpha.12-dev.5, updated by step 4 to 0.1.0-alpha.12 → keep 0.1.0-alpha.12 (step 4 works as expected).
Original: @azure-tools/azure-http-specs: 0.1.0-alpha.12-dev.2, updated to 0.1.0-alpha.11 → keep 0.1.0-alpha.12-dev.2.
Original: @azure-tools/azure-http-specs: 0.1.0-alpha.12-dev.2, updated to 0.1.0-alpha.12 → keep 0.1.0-alpha.12 (step 4 works as expected).

Run version change script:

npm run change:version

Build and commit:

npm install && npm run build && git add -u && git commit -m "bump version"

Push and create PR:

cd {REPO}
git push origin HEAD

Create PR with title [python] release new version and no description.