docs: align cache 5.7.5 publication evidence - #15
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
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.
Documentation-only follow-up for the published v5.7.5 GitHub release.
Updates README.md, ORIGIN.md, SECURITY-MAINTENANCE.md and RELEASE-NOTES-5.7.5.md to record the exact signed release source, published JAR bytes, 19 original evidence assets, 40 suites/510 tests, and exact-source CodeQL results. Gate 12 now describes the actual GitHub-asset consumer and explicitly states that no new OCI carrier was published. Historical integration observations remain distinguished from the focused 5.7.5 verification.
No code, dependency, workflow, artifact or tag changes. The official tag remains bound to a9aea56; the JAR remains SHA256 0f536a9c7bcd00f2369586fb6ca1606f7e45f3225e24795d10d38397051c8715. No local rebuild, rescan or release action was performed for this docs change. Existing required PR checks remain unchanged.