Update dependency com.vanniktech.maven.publish to v0.36.0#25
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Update dependency com.vanniktech.maven.publish to v0.36.0#25renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
664375d to
f1c5ab7
Compare
f1c5ab7 to
de76245
Compare
de76245 to
b3904bf
Compare
b3904bf to
9ff9364
Compare
9ff9364 to
0158c02
Compare
0158c02 to
e99df7f
Compare
e99df7f to
62c0378
Compare
62c0378 to
3c232f2
Compare
3c232f2 to
b613a39
Compare
b613a39 to
0085ebf
Compare
0085ebf to
0bfb812
Compare
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
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.25.3→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
v0.35.0Compare Source
com.android.kotlin.multiplatform.library.SONATYPE_HOSTis not set toCENTRAL_PORTAL.Thanks to @joshfriend, @Flowdalic and @Goooler for their contributions to this release.
Minimum supported versions
Compatibility tested up to
v0.34.0Compare Source
0.33.0 release notes for upgrade
instructions if you haven't upgraded yet.
SonatypeHosthas been removed from the DSL.SONATYPE_HOSTonly supportsCENTRAL_PORTALnow. It's recommended to use the following properties instead:mavenCentralPublishing=truereplacesSONATYPE_HOST=CENTRAL_PORTAL.mavenCentralAutomaticPublishing=truereplacesSONATYPE_AUTOMATIC_RELEASE=true.publishtasks.Thanks to @Goooler and @solrudev for their contributions to this release.
Minimum supported versions
Compatibility tested up to
v0.33.0Compare Source
BREAKING
publishToMavenCentral()andpublishToMavenCentral(automaticRelease)withoutSonatypeHostwillnow publish through the Central Portal.
publishToMavenCentralthat take aSonatypeHostparameter.SonatypeHost.New
com.android.fused-library. There are currently several limitationson the Android Gradle plugin side which make signing as well as publishing sources/javadocs not possible.
Improvements
mavenCentralPublishing=truereplacesSONATYPE_HOST=CENTRAL_PORTAL.mavenCentralAutomaticPublishing=truereplacesSONATYPE_AUTOMATIC_RELEASE=true.signAllPublications=truereplacesRELEASE_SIGNING_ENABLED=true.pomFromGradleProperties()is not called.TaskProvidertoJavadocJar.Dokka.-javadocjars (locally, the name of the published artifact is unchanged).versionto be read too early when publishing to Central Portal.Thanks to @Goooler, @solrudev and @sschuberth for their contributions to this release.
Minimum supported versions
Compatibility tested up to
v0.32.0Compare Source
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
V2Enabled.v0.31.0Compare Source
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
V2Enabled.v0.30.0Compare Source
org.jetbrains.dokka.experimental.gradle.pluginMode=V2Enabled.org.jetbrains.dokkaandorg.jetbrains.dokka-javadoc.org.jetbrains.dokka-androidplugin.httpsurl inSONATYPE_HOSTGradle property.Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
V2Enabled.v0.29.0Compare Source
configureBasedOnAppliedPlugins(sourcesJar: Boolean, javadocJar: Boolean)overload that allows disabling sources and javadoc jars without having to use the more granular
PlatformAPIs.afterEvaluateanymore, making manual overrides easier.Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
v0.28.0Compare Source
this use the
CENTRAL_PORTALoption when specifying the Sonatype host.releasevariant if the projecthas an Android target and no variant was explicitly specified through the Kotlin Gradle DSL.
KotlinMultiplatform(...).closeAndReleaseRepositorytask. UsereleaseRepository, whichis functionally equivalent, instead.
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
v0.27.0Compare Source
releaseRepositoryreleases a staging repository at the end of the build and can be executed in the same buildas the publishing task. This allows having automatic releases without permanently enabling them.
publishToMavenCentralas alias for runningpublishAllPublicationsToMavenCentralRepository.publishAndReleaseToMavenCentralas alias for running both of the above.coordinates(...)and leave the others at their default value.Thanks to @sschuberth for the contribution.
java-test-fixtureprojects being broken with Gradle 8.6.closeAndReleaseRepositoryin favor ofreleaseRepository.Minimum supported versions
Compatibility tested up to
Configuration cache status
When using Gradle 8.1 or newer configuration cache is generally supported.
Exceptions to that are:
v0.26.0Compare Source
configure(Platform)from the main plugin to modifywhat is getting published. Check out the docs for more details
configureBasedOnAppliedPluginsDSL method toallow applying the default
configurelogic of the main plugin.configure(Platform)now validates that the required plugins areapplied (e.g. Android Gradle Plugin for Android projects).
times for Gradle plugin projects with more than one publication. Thanks to
@autonomousapps for the fix.
next release, because the Kotlin/JS plugin has been deprecated.
from
simpleJavadocJartoplainJavadocJar. Thanks to @sschuberth.Minimum supported versions
Compatibility tested up to
Configuration cache status
When using Gradle 8.1 or newer configuration cache is generally supported.
Exceptions to that are:
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.