Fix Maven Central release signing#573
Merged
Merged
Conversation
devPalacio
force-pushed
the
sdk-release-signing-env
branch
from
22694f7 to
16e66a8
Compare
devPalacio
changed the title
joshafeinberg
approved these changes
Jun 26, 2026
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
2 participants
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
Fixes the main release failure in https://github.com/dropbox/dropbox-sdk-java/actions/runs/28249994309.
publishToMavenCentralfor snapshots andpublishAndReleaseToMavenCentralfor releases.:core:checkSigningConfigurationafter AWS Secrets Manager fetch so missing signatory config fails early.Test Plan
git diff --check.github/workflows/check.yml./gradlew :core:checkSigningConfigurationwithout secrets fails with the expected missing-signatory diagnostic