fix: update dependency com.vanniktech:gradle-maven-publish-plugin to v0.33.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.vanniktech:gradle-maven-publish-plugin	0.29.0 -> 0.33.0

---

Release Notes

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

v0.33.0

Compare Source

[!CAUTION]
Sonatype OSSRH (oss.sonatype.org and s01.oss.sonatype.org) will be shut down on June 30, 2025.

Migration steps:

1. Sign in to the Central Portal with your existing Sonatype account
2. Go to Namespaces and click "Migrate Namespace"
   for the relevant namespace. Confirm the migration and wait for it to complete.
3. Optional: If you want to publish snapshots of your project tap the 3 dots next to your namespace and
   select "Enable SNAPSHOTs"
4. Go to Account and select "Generate User Token". Use the shown
   "Username" and "Password" as values for mavenCentralUsername and mavenCentralPassword.
5. Configure this plugin to publish to Central Portal. Either update your SONATYPE_HOST property from
   DEFAULT or S01 to CENTRAL_PORTAL or call publishToMavenCentral()/publishToMavenCentral(automaticRelease)
   without a SonatypeHost parameter.

BREAKING

• publishToMavenCentral() and publishToMavenCentral(automaticRelease) without SonatypeHost will
  now publish through the Central Portal.
• Deprecated overloads of publishToMavenCentral that take a SonatypeHost parameter.
• Deprecated SonatypeHost.

New

• Basic experimental support for com.android.fused-library. There are currently several limitations
  on the Android Gradle plugin side which make signing as well as publishing sources/javadocs not possible.

Improvements

• Added new Gradle properties
  • mavenCentralPublishing=true replaces SONATYPE_HOST=CENTRAL_PORTAL
  • mavenCentralAutomaticPublishing=true replaces SONATYPE_AUTOMATIC_RELEASE=true
  • signAllPublications=true replaces RELEASE_SIGNING_ENABLED=true
  • Note: The old properties continue to work and there are no plans to remove them
• The base plugin is now compatible with isolated projects as long as pomFromGradleProperties() is
  not called.
• It's possible to pass a TaskProvider to JavadocJar.Dokka
• Improved naming of produced -javadoc jars (locally, the name of the published artifact is unchanged)
• Resolve issue that caused version to be read too early when publishing to
  Central Portal.

Thanks to @​Goooler, @​solrudev and @​sschuberth for their contributions to this release.

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 24
• Gradle 8.14.2
• Gradle 9.0-rc1
• Android Gradle Plugin 8.10.0
• Android Gradle Plugin 8.11.0-rc02
• Android Gradle Plugin 8.12.0-alpha06
• Kotlin Gradle Plugin 2.1.21
• Kotlin Gradle Plugin 2.2.0-RC3

v0.32.0

Compare Source

• Improve names of Central Portal deployments.
• Fix an issue where the wrong staging profile for (s01.)oss.sonatype.org was selected
  when publishing to Maven Central.
• Fix incompatibility with Kotlin 1.9.x when used through compiled plugins.
• Improve error message when not being able to detect Kotlin plugin.
• Fix an issue with detecting whether configuration cache is enabled which lead to a not
  actionable error message.
• Fix compatibility with Gradle 9.0.

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 24
• Gradle 8.14
• Gradle 9.0-milestone-6
• Android Gradle Plugin 8.10.0
• Android Gradle Plugin 8.11.0-alpha10
• Kotlin Gradle Plugin 2.1.20
• Kotlin Gradle Plugin 2.1.21-RC2
• Kotlin Gradle Plugin 2.2.0-Beta2

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

Compare Source

• Add support for publishing snapshots to Central Portal.
  • Make sure to enable snapshots for your namespace on central.sonatype.com.
  • Thanks to @​solrudev for the contribution.
• Add support for multiple matching staging profiles by taking the one with the longest
  matching prefix.

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.13
• Android Gradle Plugin 8.9.0
• Android Gradle Plugin 8.10.0-alpha07
• Kotlin Gradle Plugin 2.1.10
• Kotlin Gradle Plugin 2.1.20-RC

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

---

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 is behind base branch, 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.