Repository navigation
Allow the exact pinned source in convergence packaging - #1033
Open
GraciousGazelles wants to merge 5 commits into
Open
GraciousGazelles wants to merge 5 commits into
GraciousGazelles wants to merge 5 commits into
Conversation
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
GraciousGazelles
enabled auto-merge
November 11, 2026 14:23
This branch has not been deployed
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.
The existing convergence-package operation pins a single source SHA, tree, and upstream ancestor from its fixed branch, and runs only from protected main. A later generic ancestry check nevertheless requires that detached source to be an ancestor of the workflow host, making the approved source ineligible because it intentionally diverges from current main.
This changes only that final check: the exemption applies when the workflow has already selected the fixed
convergence_packagesource. Ordinary package and pull-request paths keep the host-ancestry requirement. The exact branch/SHA/tree/upstream checks, clean generation, artifact identity/checksums, and same-run x86_64/AArch64 package-consumer checks remain unchanged.No package artifact is published or installed by this change; after protected landing, the existing convergence-package workflow will validate the pinned source and consumer path.