Repository navigation
Updating Patch Release Process - #50712
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…s and adding tests
Jair Myree (jairmyree)
requested review from
a team,
Alan Zimmer (alzimmermsft),
Vinay Gera (g2vinay),
Praveen Kuttappan (praveenkuttappan) and
Ray Chen (raych1)
as code owners
October 8, 2026 15:35
|
Azure Pipelines: Successfully started running 2 pipeline(s). 34 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.
🔵 Needs a closer look
It changes post-publication release automation and repository-wide version reconciliation, warranting final human validation.
0 open findings
What changed in this PR
Automates deterministic patch-release merge-backs into main using a generated changelog manifest.
Changes:
- Generates and validates
patch-changelog.md. - Automates dependency, changelog, and generated POM merge-back updates.
- Adds tests and updates release documentation.
| File | Description |
|---|---|
eng/versioning/test_find_unused_dependencies.py |
Tests unused dependency removal. |
eng/versioning/find_unused_dependencies.py |
Adds dependency cleanup mode. |
eng/scripts/tests/patch-mergeback-helpers.tests.ps1 |
Tests manifest and reconciliation helpers. |
eng/scripts/tests/Create-Patch-Mergeback.tests.ps1 |
Tests end-to-end merge-back preparation. |
eng/scripts/patch-mergeback-helpers.ps1 |
Implements manifest parsing and updates. |
eng/scripts/New-PatchChangelog.ps1 |
Generates the patch manifest. |
eng/scripts/Create-Patch-Mergeback.ps1 |
Prepares merge-back changes from main. |
eng/pipelines/templates/stages/archetype-sdk-client-patch.yml |
Adds merge-back validation. |
eng/pipelines/templates/stages/archetype-java-release-patch.yml |
Creates merge-back PRs after publication. |
eng/pipelines/patch-release.yml |
Enables merge-back automation. |
eng/pipelines/Patch-Release-README.md |
Documents the new process. |
eng/pipelines/patch-release-prepare.yml |
Generates preparation artifacts. |
.github/skills/azsdk-java-patch-mergeback/SKILL.md |
Updates recovery guidance. |
.github/skills/azsdk-java-patch-mergeback/references/version-client-resolution.md |
Documents version reconciliation. |
.github/skills/azsdk-java-patch-mergeback/references/changelog-resolution.md |
Documents changelog reconciliation. |
🧠 Review effort: Balanced
Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.
Co-authored-by: Alan Zimmer <48699787+alzimmermsft@users.noreply.github.com>
Co-authored-by: Alan Zimmer <48699787+alzimmermsft@users.noreply.github.com>
Alan Zimmer (alzimmermsft)
approved these changes
Oct 20, 2026
Alan Zimmer (alzimmermsft)
approved these changes
Oct 26, 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.
This pull request introduces major improvements to the Azure SDK for Java patch release process, focusing on automation, determinism, and clarity for patch merge-back operations. The changes ensure that released patch versions, changelog entries, and POM updates are consistently and automatically merged back into
mainusing a manifest-driven approach, reducing manual intervention and errors. The documentation has also been updated to reflect these new workflows and guardrails.Patch Release and Merge-back Automation
mainafter publishing packages, using a manifest file (patch-changelog.md) to drive exact dependency version, changelog, and POM updates. Source resets, README changes, and other patch-branch-only files are excluded. [1] [2] [3]external_dependencies.txtand generates thepatch-changelog.mdmanifest, ensuring only relevant dependencies and changelog entries are included in the release. [1] [2]Manifest-driven Changelog and Dependency Resolution
patch-changelog.md, and only the exact blocks from this manifest are merged back intomain. The documentation and reconciliation guides have been updated to reflect this, clarifying that no other release-branch content is merged. [1] [2]version_client.txtis now manifest-driven: only artifacts listed inpatch-changelog.mdare updated, and only if the patch version is newer thanmain. Thecurrent-versionis always preserved frommain.Documentation and Pipeline Template Updates
patch-changelog.md, the exclusion of certain files, and the automated nature of the merge-back. [1] [2]These changes make the patch release process more robust, reproducible, and less error-prone by codifying the exact set of changes to be merged back and automating their application.