Repository navigation
Drop stale entries from the Java SDK dependency trust list - #73792
Merged
Merged
Conversation
The regenerate-java-sdk-verification-metadata hook added in apache#71869 drops checksums that no Java SDK build task resolves any more, but the trust list on main still carried entries for versions superseded by earlier dependency bumps. The hook therefore rewrites the file in every run, and static checks fail on every PR regardless of what it touches. Generated-by: Claude Opus 5
henry3260
approved these changes
Sep 27, 2026
henry3260
left a comment
Contributor
There was a problem hiding this comment.
Thanks for the quick fix
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.
The
regenerate-java-sdk-verification-metadatahook added in #71869 drops checksums that no Java SDK build task resolves any more. Butjava-sdk/gradle/verification-metadata.xmlon main still had entries for versions superseded by earlier dependency bumps (jackson 2.22.1, spotbugs-annotations 4.10.3, junit-bom 6.1.2). The hook therefore rewrites the file on every run, andCI image checks / Static checksfails on every PR regardless of what it touches (e.g. #73782).This applies exactly the diff the hook produced in CI. It only removes entries; nothing new is trusted.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5) following the guidelines
🤖 Generated with Claude Code