Repository navigation
Attest the Javadoc jar only once - #14
Merged
Merged
Conversation
The release Javadoc jar is the same file as the one in the Maven layout, and the attestation API rejects duplicate subjects. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QwfmMR3bsQCfffkJXMD6m2
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
The 1.10.1 release failed in
Attest build provenancewithduplicate subject in statement: the release Javadoc jar is the same file as the one in the Maven layout. It is now attested once, frommaven/;gh attestation verifymatches the release asset by digest.Tag 1.10.1 was not created, so merging this releases 1.10.1.
Generated by Claude Code