http-client-python-bump-and-release
Streamline dependency bumps and version releases for the http-client-python package with automated PR preparation.
Install
mkdir -p .claude/skills/http-client-python-bump-and-release && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5251" && unzip -o skill.zip -d .claude/skills/http-client-python-bump-and-release && rm skill.zipInstalls to .claude/skills/http-client-python-bump-and-release
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create a PR to bump TypeSpec/Azure Tools dependencies, update peer dependencies, or release a new version of the http-client-python package.Key capabilities
- →Generates release branch with MM-DD format
- →Updates TypeSpec and Azure-tools dependencies
- →Syncs peerDependencies while maintaining range formats
- →Preserves specific dev dependency alpha/dev versions
How it works
Executes a sequence of git reset/pull operations and calls npm-check-updates with specific version filters.
Inputs & outputs
When to use http-client-python-bump-and-release
- →Bump TypeSpec dependencies
- →Update Azure-tools versions
- →Prepare a new release branch for Python HTTP clients
- →Sync package.json peer dependencies
About this skill
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 themicrosoft/typespecrepository.
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
peerDependenciesin package.json:- If format is
">=0.a.b <1.0.0": Update only the0.a.bportion, keep the range format unchanged - If format is
"^1.a.b": Update to the latest version
- If format is
-
Verify
devDependenciesversions for specs:- Check
@typespec/http-specsand@azure-tools/azure-http-specs - If the original version in
package.jsonis 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 to0.1.0-alpha.11→ keep0.1.0-alpha.12-dev.5. - Original:
@typespec/http-specs: 0.1.0-alpha.12-dev.5, updated by step 4 to0.1.0-alpha.12→ keep0.1.0-alpha.12(step 4 works as expected). - Original:
@azure-tools/azure-http-specs: 0.1.0-alpha.12-dev.2, updated to0.1.0-alpha.11→ keep0.1.0-alpha.12-dev.2. - Original:
@azure-tools/azure-http-specs: 0.1.0-alpha.12-dev.2, updated to0.1.0-alpha.12→ keep0.1.0-alpha.12(step 4 works as expected).
- Check
-
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 versionand no description.
When not to use it
- →Updating repositories outside of microsoft/typespec
- →Manually editing dependencies without following the branch flow
Prerequisites
Limitations
- →Requires manual verification of version strings
- →Limited to specific package namespaces (@typespec, @azure-tools)
How it compares
It follows a strict, predefined manual versioning logic for dev-alpha packages that generic update tools would break.
Compared to similar skills
http-client-python-bump-and-release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| http-client-python-bump-and-release (this skill) | 1 | 6mo | Review | Intermediate |
| dev | 2 | 6mo | Review | Advanced |
| release-skills | 2 | 3mo | Review | Intermediate |
| takopi-release | 1 | 3mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by microsoft
View all by microsoft →You might also like
dev
atopile
LLM-focused workflow for working in this repo: compile Zig, run the orchestrated test runner, consume test-report.json/html artifacts, and discover/debug ConfigFlags.
release-skills
JimLiu
Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送".
takopi-release
banteg
Prepare and ship a Takopi release. Use when asked to cut a release, bump release versions, update changelog/spec/readme, tag v<major.minor.patch>, or trigger the GitHub release workflow.
testing
hw-native-sys
Testing guide and pre-commit testing strategy for PTO Runtime. Use when running tests, adding tests, or deciding what to test before committing.
ci-pr-helper
lance-format
Run local test/style checks and open GitHub PRs for lance-context. Use when asked to run CI-equivalent checks (uv pytest, ruff/pyright, cargo fmt/clippy/test) and then create a PR with a proper title/body.
auto_pr
splendidsummer
auto_pr — an agent skill by splendidsummer.