Document emergency hotfix release process - #9784
Open
Rick Winter (RickWinter) wants to merge 3 commits into
Open
Document emergency hotfix release process#9784Rick Winter (RickWinter) wants to merge 3 commits into
Rick Winter (RickWinter) wants to merge 3 commits into
Conversation
|
Azure Pipelines: Successfully started running 18 pipeline(s). 3 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Copilot review overview
Review tier: Balanced
Findings: 1
New issues introduced by this change (1)
| Severity | Finding |
|---|---|
 |
docs/guides/emergency-hotfix-release.md — The example base tag azure-dev-cli_1.32.0 predates this PR, so its copy of publish-cli.yml… |
What changed in this PR
Documents and enables emergency patch releases from an existing CLI release tag.
Changes:
- Adds the emergency hotfix release guide.
- Links the guide from the documentation index.
- Targets GitHub releases at the pipeline source commit.
| File | Description |
|---|---|
eng/pipelines/templates/steps/publish-cli.yml |
Pins release tags to Build.SourceVersion. |
docs/README.md |
Links the hotfix guide. |
docs/guides/emergency-hotfix-release.md |
Documents preparation, publishing, verification, and cleanup. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
JeffreyCA
approved these changes
Aug 28, 2026
…hotfix-cherry-pick
Contributor
There was a problem hiding this comment.
Copilot review overview
Review tier: Balanced
Findings: None
Issues resolved since last review (1)
| Severity | Finding |
|---|---|
|
docs/guides/emergency-hotfix-release.md — The example base tag azure-dev-cli_1.32.0 predates this PR, so its copy of publish-cli.yml… View resolved comment |
Suppressed comments (1)
docs/guides/emergency-hotfix-release.md:26
- A branch cut from an existing release tag that predates this PR will not contain the new
--targetargument. Azure Pipelines resolves this same-repository template from the selected hotfix branch, so the first such release would still run the old template and could tagmain. Require the pipeline-support change on the hotfix branch before applying the product fix.
An authorized maintainer creates the short-lived `hotfix/azd-1.32.1` branch in `Azure/azure-dev`
from the immutable `azure-dev-cli_1.32.0` release tag.
Contributor
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash: pwsh: WindowsPowerShell install MSI install Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
Comment on lines
+16
to
+17
| global `release/latest` channel and, for a stable version, the global `release/stable` channel. Contact | ||
| the engineering systems team before servicing an older release line because publishing it through the |
There was a problem hiding this comment.
The main issue here when releasing hotfixes for older versions is that the version.txt file update stage should NOT be run.
Doing so would cause unexpected behavior with client upgrade code paths.
Consider these 2 scenarios:
Version requiring hotfix: 1.2.2 -> 1.2.3 (hotfixed version)
Latest release: 1.2.6
Hotfix release: 1.2.3
Client version: 1.2.5
Client sees: no upgrade message because hotfix release is less than current version
Latest release: 1.2.6
Hotfix release: 1.2.3
Client version: 1.2.0
Client sees: Upgrade to 1.2.3 (not 1.2.6)
Contributor
There was a problem hiding this comment.
azd update will run into this issue. We may want to limit the hotfixes to be on latest release version?
| `eng/pipelines/templates/steps/publish-cli.yml` passes `--target "$(Build.SourceVersion)"` to | ||
| `gh release create`. If the source release tag predates that safeguard, include the same pipeline | ||
| change in the hotfix pull request. Without it, GitHub creates the release tag from `main` instead of | ||
| the commit that produced the hotfix artifacts. |
There was a problem hiding this comment.
Other changes like CFS may necessitate that the eng/ folder be brought over from its current state of main. It's possible that some things could break in those situations.
Daniel Jurek (danieljurek)
approved these changes
Aug 31, 2026
Daniel Jurek (danieljurek)
left a comment
Daniel Jurek (danieljurek)
left a comment
Member
There was a problem hiding this comment.
Approve change to publish-cli.yml --target should be used because it defaults to the head of the default branch if left off.
Marina He (hemarina)
approved these changes
Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mainValidation
cspell lint "docs/guides/emergency-hotfix-release.md" "docs/README.md" "eng/pipelines/templates/steps/publish-cli.yml" --relative --config ./.vscode/cspell.misc.yaml --no-progressgit diff --checkFixes #7712