# Create Hotfix

> Create a hotfix (patch) release branch for an Azure SDK Rust crate.

- Skill: `azure-azure-sdk-for-rust/create-hotfix` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add azure-azure-sdk-for-rust/create-hotfix`
- Raw SKILL.md: https://api.skillmd.com/api/skills/azure-azure-sdk-for-rust/create-hotfix/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: Azure (https://skillmd.com/u/azure-azure-sdk-for-rust)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/azure-azure-sdk-for-rust/create-hotfix

---


# Create a Hotfix

Use the bundled script for deterministic discovery and git operations. Run all commands from the repository root.

1. List workspace crates:

   ```bash
   python3 .github/skills/create-hotfix/create_hotfix.py list-crates
   ```

   Use a single-select prompt to ask the user which crate to patch, using the
   crate names from the JSON output.

2. Prepare the hotfix:

   ```bash
   python3 .github/skills/create-hotfix/create_hotfix.py prepare <crate-name>
   ```

   The command fetches tags and `main` directly from `https://github.com/Azure/azure-sdk-for-rust`, finds the latest stable `<crate-name>@<version>` tag, calculates the next patch version, creates `hotfix/<crate-name>-<version>` from that tag unless already on a `hotfix/` branch, and returns candidate commits from `main` as JSON.

3. If candidates were returned, prompt the user with a multiselect containing
   each candidate's SHA and deterministic summary. Allow selecting none.

4. If commits are selected, preserve their displayed order and run:

   ```bash
   python3 .github/skills/create-hotfix/create_hotfix.py cherry-pick <sha>...
   ```

   The script automatically resolves `Cargo.lock` conflicts by taking `--ours`,
   then regenerating it with:

   ```bash
   cargo generate-lockfile --manifest-path Cargo.toml
   ```

   If the JSON result has a `waiting` status, prompt the user to resolve and
   stage the listed conflicts. Remain waiting for the user to confirm they are
   ready, then run:

   ```bash
   python3 .github/skills/create-hotfix/create_hotfix.py continue
   ```

   Repeat this step if another commit conflicts. Do not abort or skip commits.
   Only show the final message after the script returns a `complete` status.

5. Report the selected crate, base tag, patch version, branch, and cherry-picked commits. Tell the user:

   > Make any additional hotfix changes on this branch. Do not merge this branch
   > into `main`; cherry-pick any new fixes into `main` separately. See the
   > [Azure SDK hotfix branch policy](https://azure.github.io/azure-sdk/policies_repobranching.html#hotfix-branches)
   > for more information.