Harden release integrity and refresh security dependencies - #9
Merged
Merged
Conversation
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.
Summary
actions/setup-javato the already-tested v6.0.1 immutable commit;v0.3.3validation-build/release-asset digest mismatch;Security rationale
Jackson Databind 2.22.3 includes fixes for CVE-2026-91776 and CVE-2026-91777. The release workflow also prevents a repeat of the current
v0.3.3provenance mismatch by refusing version/tag divergence and by generating the checksum from the exact JAR that is staged for publication.Release safety
The release workflow refuses to publish when:
No product behavior or target-request semantics are changed by this PR.