chore(deps): update plugin maven-publish to v0.30.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.vanniktech.maven.publish.base	0.27.0 -> 0.30.0

---

Release Notes

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

v0.30.0

Compare Source

• Add support for Dokka 2.0.0-Beta
  • Supports org.jetbrains.dokka.experimental.gradle.pluginMode=V2Enabled
  • Supports both org.jetbrains.dokka and org.jetbrains.dokka-javadoc
  • If both are applied the javadoc output is published
  • Removed support for the old org.jetbrains.dokka-android plugin
• Support custom Sonatype hosts by providing a https url in SONATYPE_HOST Gradle property
• Remove usages of deprecated Gradle API that is scheduled to be removed in Gradle 9.0
• Raised minimum supported Gradle version
• Improve naming of javadoc jars

Minimum supported versions

• JDK 11
• Gradle 8.5
• Android Gradle Plugin 8.0.0
• Kotlin Gradle Plugin 1.9.20

Compatibility tested up to

• JDK 23
• Gradle 8.10.2
• Android Gradle Plugin 8.7.0
• Android Gradle Plugin 8.8.0-alpha05
• Kotlin Gradle Plugin 2.0.20
• Kotlin Gradle Plugin 2.1.0-Beta1

Configuration cache status

Configuration cache is generally supported, except for:

• Publishing releases to Maven Central (snapshots are fine), blocked by Gradle issue #​22779.
• When using Dokka 1.x or Dokka 2.x without V2Enabled

v0.29.0

Compare Source

• Added configureBasedOnAppliedPlugins(sourcesJar: Boolean, javadocJar: Boolean)
  overload that allows disabling sources and javadoc jars without having to use
  the more granular Platform APIs.
• For Java library and Kotlin/JVM projects the Gradle module metadata now properly
  includes the sources jar.
• When running on Gradle 8.8 or newer the pom configuration is not applied in
  afterEvaluate anymore, making manual overrides easier.
• Fix potential issue with the javadoc jar tasks that can cause Gradle to disable
  optimizations.
• When staging profiles can't be loaded the status code of the response is added
  to the error message.

Minimum supported versions

• JDK 11
• Gradle 8.1
• Android Gradle Plugin 8.0.0
• Kotlin Gradle Plugin 1.9.20

Compatibility tested up to

• JDK 21
• Gradle 8.8
• Android Gradle Plugin 8.5.0
• Android Gradle Plugin 8.6.0-alpha06
• Kotlin Gradle Plugin 2.0.0
• Kotlin Gradle Plugin 2.0.20-Beta1

Configuration cache status

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

v0.28.0

Compare Source

• 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.

Minimum supported versions

• JDK 11
• Gradle 8.1
• Android Gradle Plugin 8.0.0
• Kotlin Gradle Plugin 1.9.20

Compatibility tested up to

• JDK 21
• Gradle 8.6
• Gradle 8.7-rc-3
• Android Gradle Plugin 8.3.0
• Android Gradle Plugin 8.4.0-alpha13
• Kotlin Gradle Plugin 1.9.23
• Kotlin Gradle Plugin 2.0.0-Beta4

Configuration cache status

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

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.