Update gradle publishing method - #139
Merged
Merged
Conversation
michaelwiltfong-okta
approved these changes
Oct 21, 2025
michaelwiltfong-okta
approved these changes
Oct 21, 2025
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.
Description
The previous gradle publish method is now incompatible given that the OSSRH has been sunset
We now provide the correct method to publish a build via:
./gradlew :guardian:publishToMavenCentralReferences
https://auth0team.atlassian.net/browse/MFA-4054
Testing
When running the provided command, we see the build in Maven Central:
Checklist