Bump gradle maven publish plugin from 0.21.0 to 0.25.3 #810
Conversation
This file contains 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
msridhar
changed the title
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.
Changelog for plugin
We have to do some renaming as the
javaSourcesJarconfiguration is now justsourcesJar. Also, the:nullaway:buildWithNullAwaypreviously used a hacky way to refer to the current NullAway jar that broke with this upgrade. Here we clean things up to refer to the current jar more directly.The plugin has better integration with Sonatype and will close the staging repository after all artifacts are uploaded. There is an option to automatically release as well, but I haven't enabled that for now (it makes testing of release uploads difficult), so you still need to go to https://oss.sonatype.org to finalize the release. Relatedly, apparently we don't need
--no-daemonand--no-parallelflags anymore when cutting a release; updated the release docs accordingly.I tested locally and confirmed that the exact same number of files get included in the jar-infer-cli shadow jar, and that cutting a real release successfully uploads to Maven Central.