Fix patched Jackson runtime and immutable cache input for 0.183.328 - #64
Merged
Merged
Conversation
chen21019
force-pushed
the
verification/orchestration-engine-0.183.328
branch
from
October 1, 2026 05:15
3170a46 to
ad43f4b
Compare
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.
Scope
Update the two required Jackson runtime lines to 2.22.3 / 3.2.3 and consume the officially published Cache 5.7.5 JAR by exact source, asset ID and SHA256. Preserve platform behavior, WebAuthn4J, patchless annotations and the distinct Jackson namespaces. Normalize multi-release class paths in the existing JAR namespace gate and reject foreign classes.
Validation
Four focused offline test groups pass, including root/MR namespace fixtures. Seven Java regression cases were added for the real gdapi mapper and WebAuthn4J JSON/CBOR credential roundtrip; compilation/execution, all-module tests, artifact/SBOM scans, exact-source CodeQL and isolated startup remain pending in the official verification workflows. Cache producer results are not Engine compatibility evidence.
Release boundary
Do not overwrite older tags or artifacts. Publish the retained CI bytes only after all relevant gates pass; no production deployment, HAProxy change, runtime patch or weaker exception policy. Candidate documentation states the current verification status.