Update plugin mavenPublish to v0.36.0 #2070
Merged
+1
−1
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.
This PR contains the following updates:
0.35.0→0.36.0Release Notes
vanniktech/gradle-maven-publish-plugin (com.vanniktech.maven.publish)
v0.36.0Compare Source
BREAKING
DirectorySignatureTypeinternal.Behavior changes
validateDeploymentnow has theDeploymentValidationenum as type instead of being a boolean. The defaultis now to just wait for the
VALIDATEDstate. The previous behavior can be achieved by setting it toPUBLISHED.NONEcan be used for disabling the validation completely.configure(...)manually to configure what to publish and not passingjavadocJarexplicity,the plugin now defaults to publishing an empty javadoc jar.
Features
when using the default options and the Dokka plugin is applied to the project.
JavadocJarandSourcesJaroptions toconfigureBasedOnAppliedPluginsand to allapplicable project types that can be passed to
configure. The previousBooleanbased versions havebeen deprecated.
mavenCentralDeploymentValidationandmavenCentralAutomaticPublishingare used for the default values of the 2 parameters when they are not passedexplicitly. This allows to more easily override them in certain environments.
gradle.propertiesfiles are now considered inthe same way they are when isolated projects is disabled.
Improvements
Minimum supported versions
Compatibility tested up to
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.