How do I install the HTTP Client Python Bump And Release skill?

Run npx skillmds@latest add microsoft/http-client-python-bump-and-release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is HTTP Client Python Bump And Release safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with HTTP Client Python Bump And Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is HTTP Client Python Bump And Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published HTTP Client Python Bump And Release?

Microsoft (@microsoft) published this skill. Their other Agent Skills are listed on their SkillMD profile.

HTTP Client Python Bump And Release by microsoft

Name: HTTP Client Python Bump And Release
Author: Microsoft

File contents

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.

---name: http-client-python-bump-and-releasedescription: 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 ReleaseCreate 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.## PrerequisitesBefore starting, verify that `npm-check-updates` is available:```bashnpx npm-check-updates --version```If the command fails or prompts for installation, install it globally:```bashnpm install -g npm-check-updates```## Workflow1. Navigate to the package directory: ```bash cd {REPO}/packages/http-client-python ```2. Reset and sync with main: ```bash git reset HEAD && git checkout . && git checkout origin/main && git pull origin main ```3. Create release branch (use current date in MM-DD format): ```bash git checkout -b publish/python-release-{MM-DD} ```4. Update dependencies: ```bash npx npm-check-updates -u --filter @typespec/*,@azure-tools/* --packageFile package.json ```5. 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 version6. 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).7. Run version change script: ```bash npm run change:version ```8. Build and commit: ```bash npm install && npm run build && git add -u && git commit -m "bump version" ```9. Push and create PR: ```bash cd {REPO} git push origin HEAD ```10. Create PR with title `[python] release new version` and no description.

Frequently asked questions

HTTP Client Python Bump And Release