Repository navigation
Start the next patch batch after each verified release - #1049
Merged
Kuddev merged 1 commit intoNov 20, 2026
Merged
Conversation
Kuddev
merged commit Nov 20, 2026
a6d72a2
into
fix/history-private-diagnostics-1119
24 of 29 checks passed
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.
After a verified batch publishes, the stable workflow now creates the next patch branch from the public version tag. For example, publishing 2.6.1 opens
release/auto-2.6.2with a manifest based onv2.6.1and zero fixes. The next verified backport supplies the new version metadata and bilingual notes. The existing ten-fix threshold and package verification still govern publication.The workflow checks the current public Latest release before opening the branch. A retry preserves commits already on a branch descended from that tag. A conflicting branch based on unrelated history stops the job.
This is stacked on the reviewed integration in #1048. The release, CI and batch suites passed 49 tests. The bare-remote integration covered two consecutive releases, an existing branch with additional work, a conflicting branch, an unpublished commit and a dirty checkout. Architecture and whitespace checks passed.
Shared native validation
The head of this stack includes the reviewed code from #1022, #1037, #1038, #1039, #1040, #1041, #1043, #1045, #1046, #1047, #1048, together with this release-batch change. Each component retains its own diff and focused review. The combined commit
9dc808105b88and its GitHub test merge have identical trees (bf360a55c159). The shared native run exercises the combined checkout on Linux, Windows x64 and ARM64, and both macOS architectures. Packaging-specific acceptance remains attached to its own change.