Fix release signing key ID format - #3105
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.
The release deployment failed at
:lib:signMavenPublicationbecause Gradle rejects the 16-digit signing key ID0xFA5C18CFB74EC7C6(failed run).Use the same signing subkey's eight-digit ID,
0xB74EC7C6, and retain the full ID in a comment. This PR targetsrelease.Validation:
actionlint .github/workflows/deploy.ymlandgit diff --checkpassed. A check against Gradle 9.7.1's actualPgpKeyIdparser reproduced the long-ID rejection and confirmed the short ID is accepted and matches the full subkey ID. No live signing or publishing was performed.