Repository navigation
fix(security): inherit patched Maven JDK images - #4
Merged
Merged
Conversation
danbao
marked this pull request as ready for review
October 22, 2026 13:20
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.
Propagate the CVE-2026-91403 JDK certificate-distrust mitigation through the updated Maven base in all 15 Node 22/24/26 × JDK 8/11/17/21/25 variants. Use exact Maven/JDK patch tags and pull the current upstream manifest. Preserve Node 22.23.4 / 24.22.1 / 26.12.1, the Docker Hub donor, libatomic1 dependency and latest selection.
Add PR image builds without publication to validate both architectures before merging; master builds retain publication and scanning. Rebuilt Node/JDK-major tags must publish completely before the web-tools security rebuild.
Validation: PR CI 39784499830 passed all 15 variants on amd64 and arm64. JDK and Maven security publication completed successfully; all new Maven GHCR manifests were checked for both architectures, expected Java patches, Maven versions and inheritance of the verified JDK layers. Matrix consistency, workflow syntax and diff checks passed.