Skip to content

chore(deps): update plugin mavenpublish to v0.37.0 - #1312

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/com.vanniktech.maven.publish-0.x
Closed

chore(deps): update plugin mavenpublish to v0.37.0#1312
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/com.vanniktech.maven.publish-0.x

Conversation

@renovate

@renovate renovate Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
com.vanniktech.maven.publish 0.27.00.37.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

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

v0.37.0

Compare Source

  • When publishing to Maven Central, redundant checksum files are now excluded by default: checksums of .asc
    signature files (gradle/gradle#20232) and the sha256/sha512
    checksums, which are never read by Gradle or Maven Central. The published checksums can be configured through
    checksums(...) in the DSL or the mavenCentralChecksums Gradle property (default md5,sha1). Signature checksum
    exclusion can be controlled through excludeSignatureChecksums() or the mavenCentralExcludeSignatureChecksums
    Gradle property.
  • Maven Central deployment id is being logged after upload.
Minimum supported versions
  • JDK 17
  • Gradle 9.0.0
  • Android Gradle Plugin 8.13.0
  • Kotlin Gradle Plugin 2.2.0
Compatibility tested up to
  • JDK 26
  • Gradle 9.6.0
  • Gradle 9.7.0-milestone-1
  • Android Gradle Plugin 9.2.1
  • Android Gradle Plugin 9.3.0-rc01
  • Android Gradle Plugin 9.4.0-alpha01
  • Kotlin Gradle Plugin 2.4.0

v0.36.0

Compare Source

BREAKING

  • Updated minimum supported JDK, Gradle, Android Gradle Plugin and Kotlin versions.
  • Removed support for Dokka v1, it's now required to use Dokka in v2 mode.
  • Mark DirectorySignatureType internal.

Behavior changes

  • validateDeployment now has the DeploymentValidation enum as type instead of being a boolean. The default
    is now to just wait for the VALIDATED state. The previous behavior can be achieved by setting it to PUBLISHED.
    NONE can be used for disabling the validation completely.
  • When calling configure(...) manually to configure what to publish and not passing javadocJar explicity,
    the plugin now defaults to publishing an empty javadoc jar.

Features

  • Android projects now support using Dokka for javadoc creation, this will happen automatically
    when using the default options and the Dokka plugin is applied to the project.
  • Added consistent JavadocJar and SourcesJar options to configureBasedOnAppliedPlugins and to all
    applicable project types that can be passed to configure. The previous Boolean based versions have
    been deprecated.
  • When enabling Maven Central publishing through the DSL, the mavenCentralDeploymentValidation and
    mavenCentralAutomaticPublishing are used for the default values of the 2 parameters when they are not passed
    explicitly. This allows to more easily override them in certain environments.
  • When isolated projects is enabled the module/project specific gradle.properties files are now considered in
    the same way they are when isolated projects is disabled.

Improvements

  • Better error message when Maven Central credentials are missing.
Minimum supported versions
  • JDK 17
  • Gradle 9.0.0
  • Android Gradle Plugin 8.13.0
  • Kotlin Gradle Plugin 2.2.0
Compatibility tested up to
  • JDK 25
  • Gradle 9.3.0
  • Gradle 9.4.0-milestone-4
  • Android Gradle Plugin 8.13.2
  • Android Gradle Plugin 9.0.0
  • Android Gradle Plugin 9.1.0-alpha05
  • Kotlin Gradle Plugin 2.3.0
  • Kotlin Gradle Plugin 2.3.20-Beta1

v0.35.0

Compare Source

  • Add support for publishing Kotlin Multiplatform libraries that use com.android.kotlin.multiplatform.library.
  • Add support for validating deployments to Central Portal
  • Raise minimum Gradle version to 8.13
  • Raise minimum Android Gradle Plugin version to 8.2.2
  • Do not unconditionally disable DocLint
  • Fail publishing if SONATYPE_HOST is not set to CENTRAL_PORTAL.
  • Fix misleading error message when Android library variant is not found.
  • Downgrade transitive OkHttp version.
  • Don't check project heirarchy for POM properties when Isolated proejcts is enabled.

Thanks to @​joshfriend, @​Flowdalic and @​Goooler for their contributions to this release.

Minimum supported versions
  • JDK 11
  • Gradle 8.13
  • Android Gradle Plugin 8.2.2
  • Kotlin Gradle Plugin 1.9.20
Compatibility tested up to
  • JDK 24
  • Gradle 9.2.0
  • Gradle 9.3.0-milestone-1
  • Android Gradle Plugin 8.13.1
  • Android Gradle Plugin 9.0.0-alpha14
  • Kotlin Gradle Plugin 2.2.21
  • Kotlin Gradle Plugin 2.3.0-Beta2

v0.34.0

Compare Source

  • Added configuration cache support for publishing.
  • Removed support for publishing through Sonatype OSSRH since it has been shut down. See the
    0.33.0 release notes for upgrade
    instructions if you haven't upgraded yet.
    • SonatypeHost has been removed from the DSL.
    • SONATYPE_HOST only supports CENTRAL_PORTAL now. It's recommended to use the following properties instead:
      • mavenCentralPublishing=true replaces SONATYPE_HOST=CENTRAL_PORTAL.
      • mavenCentralAutomaticPublishing=true replaces SONATYPE_AUTOMATIC_RELEASE=true.
  • Update the Central Portal Publisher APIs to the latest.
  • It's now possible to mix SNAPSHOT versions and release versions when running publish tasks.
  • Fixed Gradle's deprecation warning caused by invalid URI.
  • Fixed check for the minimum supported Gradle version running too late in some cases.

Thanks to @​Goooler and @​solrudev 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.3
  • Gradle 9.0.0-rc2
  • Android Gradle Plugin 8.11.1
  • Android Gradle Plugin 8.12.0-alpha08
  • Kotlin Gradle Plugin 2.2.0
  • Kotlin Gradle Plugin 2.2.20-Beta1

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.

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: (UTC)

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

@renovate
renovate Bot force-pushed the renovate/com.vanniktech.maven.publish-0.x branch from da3b4c3 to 6a61834 Compare June 23, 2026 07:25
@renovate
renovate Bot force-pushed the renovate/com.vanniktech.maven.publish-0.x branch from 6a61834 to cf6b45a Compare June 23, 2026 09:32
@renovate

renovate Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: gradle/libs.versions.toml
Command failed: ./gradlew -Dorg.gradle.jvmargs=-Xms512m -Xmx512m --console=plain --dependency-verification lenient -q properties
#=#=#                                                                          

#######################################################                   77.0%
######################################################################## 100.0%
#=#=#                                                                          

######################################################################## 100.0%
#=#=#                                                                          

######################################################################## 100.0%
#=#=#                                                                          

######################################################################## 100.0%
#=#=#                                                                          

#########################################                                 57.4%
######################################################################## 100.0%
#=#=#                                                                          

######################################################################## 100.0%

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':examples:android-ndk'.
> com.android.builder.sdk.LicenceNotAcceptedException: Failed to install the following Android SDK packages as some licences have not been accepted.
     ndk;24.0.8215888 NDK (Side by side) 24.0.8215888
  To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
  All licenses can be accepted using the sdkmanager command line tool:
  sdkmanager.bat --licenses
  Or, to transfer the license agreements from one workstation to another, see https://developer.android.com/studio/intro/update.html#download-with-gradle
  
  Using Android SDK: /home/ubuntu/.android-sdk

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Get more help at https://help.gradle.org.

BUILD FAILED in 7m 14s

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit cf6b45a. Configure here.

Comment thread gradle/libs.versions.toml
dokka = { id = "org.jetbrains.dokka", version = "1.9.20" }
spotless = { id = "com.diffplug.spotless", version = "8.7.0" }
mavenPublish = { id = "com.vanniktech.maven.publish", version = "0.27.0" }
mavenPublish = { id = "com.vanniktech.maven.publish", version = "0.37.0" }

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maven publish needs Gradle 9

High Severity

Bumping com.vanniktech.maven.publish to 0.37.0 while the wrapper stays on Gradle 8.14.5 conflicts with that release’s minimum Gradle 9.0.0 (from 0.36.0). The catalog is used by plugin-build and sentry-kotlin-compiler-plugin, so preMerge, :check, and snapshot publish are likely to fail at configuration.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit cf6b45a. Configure here.

@renovate

renovate Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (0.37.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate
renovate Bot deleted the renovate/com.vanniktech.maven.publish-0.x branch June 23, 2026 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant