Repository navigation
Converge server 1.6.519 as a verified same-tree commit - #268
Merged
chen21019 merged 4 commits intoOct 11, 2026
Merged
Conversation
Replaces #267. The old PR was squash-merged ONLY into staging/signed-server-final28-20261011T025000Z-07ae517bac, NOT into main. This replacement still requires its own protected-main checks and merge. Reviewed previous head: 6b0b206 Approved exact Git tree, including modes: 4f129b5 Original producer: fd9d9b2 Original artifact/image SHA-256: 498ad827ee21d5ec331f71fd2d1eb69b7941b0a089e773b3c7a3cd80744931ff Existing Engine 0.183.335 evidence is 9 suites / 170 JUnit tests, 0 failures / 0 errors / 0 skipped, from producer 8fd5e7d3021507647064da1ae9c9c3a6eeb4c725. Those tests were NOT rerun by this ancestry-convergence operation. No runtime bytes or file modes are intentionally changed. The new commit does not relabel the original producer or establish a new build, release, deployment, or runtime acceptance. Old-SHA checks are not carried forward. Server CodeQL queuing remains an independent required-check gate.
Preserve extended queries, local and remote threat models, and the existing required check names. Compile Go and Java using the release toolchains. No runtime source changes.
Run the required four-language workflow after migration to advanced setup. Cancel only superseded runs for the same PR or branch, preserving all required analysis and protection.
Use the distribution API name for the same production Java 25.0.4+7 LTS compiler. No runtime source or analysis scope changes.
chen21019
deleted the
staging/signed-server-final28-20261011T025000Z-07ae517bac
branch
October 11, 2026 05:58
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
1 participant
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.
Replaces #267.
The old PR was squash-merged ONLY into staging/signed-server-final28-20261011T025000Z-07ae517bac, NOT into main. This replacement still requires its own protected-main checks and merge.
Reviewed previous head: 6b0b206
Approved exact Git tree, including modes: 4f129b529562d01777c6a1d7c4fae353b3801807
Original producer: fd9d9b2
Original artifact/image SHA-256: 498ad827ee21d5ec331f71fd2d1eb69b7941b0a089e773b3c7a3cd80744931ff
Existing Engine 0.183.335 evidence is 9 suites / 170 JUnit tests, 0 failures / 0 errors / 0 skipped, from producer 8fd5e7d3021507647064da1ae9c9c3a6eeb4c725. Those tests were NOT rerun by this ancestry-convergence operation.
No runtime bytes or file modes are intentionally changed. The new commit does not relabel the original producer or establish a new build, release, deployment, or runtime acceptance. Old-SHA checks are not carried forward. Server CodeQL queuing remains an independent required-check gate.