PrettyPersianNumbers Update plugin com.vanniktech.maven.publish to v0.28.0

Update plugin com.vanniktech.maven.publish to v0.28.0

Open renovate[bot] opened this issue 6 months ago • 3 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.vanniktech.maven.publish	`0.25.3` -> `0.28.0`

vanniktech/gradle-maven-publish-plugin (com.vanniktech.maven.publish)

Added support for publishing through the new Central Portal. To use this use the CENTRAL_PORTAL option when specifying the Sonatype host.
For Kotlin Multiplatform the main plugin will now automatically publish the release variant if the project has an Android target and no variant was explicitly specified through the Kotlin Gradle DSL.
Support specifying the Android variants to publish in KotlinMultiplatform(...).
Updated minimum supported Gradle, Android Gradle Plugin and Kotlin versions.
Removed support for the deprecated Kotlin/JS plugin.
Removed the deprecated closeAndReleaseRepository task. Use releaseRepository, which is functionally equivalent, instead.

Configuration cache is generally supported, except for:

Publishing releases to Maven Central (snapshots are fine), blocked by Gradle issue #22779.
Dokka does not support configuration cache

Added new publishing related tasks
- releaseRepository releases a staging repository at the end of the build and can be executed in the same build as the publishing task. This allows having automatic releases without permanently enabling them.
- publishToMavenCentral as alias for running publishAllPublicationsToMavenCentralRepository.
- publishAndReleaseToMavenCentral as alias for running both of the above.
- For more information checkout the docs.
It is now possible to only pass a subset of the parameters to coordinates(...) and leave the others at their default value. Thanks to @sschuberth for the contribution.
Fixed java-test-fixture projects being broken with Gradle 8.6.
Deprecated closeAndReleaseRepository in favor of releaseRepository.

When using Gradle 8.1 or newer configuration cache is generally supported.

Exceptions to that are:

Publishing releases to Maven Central (snapshots are fine), blocked by Gradle issue #22779.
Dokka does not support configuration cache

It's now supported to call configure(Platform) from the main plugin to modify what is getting published. Check out the docs for more details
The base plugin now has a configureBasedOnAppliedPlugins DSL method to allow applying the default configure logic of the main plugin.
Calling configure(Platform) now validates that the required plugins are applied (e.g. Android Gradle Plugin for Android projects).
It's now possible to disable source publishing for KMP projects.
Fixed an issue which would cause the javadoc jar task to be registered multiple times for Gradle plugin projects with more than one publication. Thanks to @autonomousapps for the fix.
Publishing Kotlin/JS projects has been deprecated and will be removed in the next release, because the Kotlin/JS plugin has been deprecated.
The internal task to create a javadoc jar for certain project types has been renamed from simpleJavadocJar to plainJavadocJar. Thanks to @sschuberth.