chore: bump com.vanniktech.maven.publish from 0.30.0 to 0.37.0

[dependabot]

Bumps com.vanniktech.maven.publish from 0.30.0 to 0.37.0.

Release notes

Sourced from com.vanniktech.maven.publish's releases.

0.37.0

• 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

0.37.0-rc1

• 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

0.36.0

BREAKING

... (truncated)

Changelog

Sourced from com.vanniktech.maven.publish's changelog.

0.37.0 (2026-06-21)

• 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

0.36.0 (2026-01-13)

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

... (truncated)

Commits

• 7017e3d enable feature preview (#1381)
• 05f6b6e use 0.37.0-rc1 (#1380)
• 0167c9c Changelog for 0.37.0 (#1379)
• b652eb3 Update dependency java to v26 (#1353)
• a9f70b3 Update dependency com.freeletics.gradle:scripts-formatting-jvm to v0.37.0 (#1...
• 541cf8f Log deployment id and publishing type after Central Portal upload (#1354)
• d4873e5 Update slf4j monorepo to v2 (#1365)
• 42baf9d Update android.gradle (#1335)
• 2de1978 Update Gradle (#1362)
• 6f03e46 Update kotlin monorepo to v2.4.0 (#1352)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cursor]

PR Summary

Medium Risk
Publishing plugin jumps several minor versions with documented breaking changes (validation, javadoc defaults) and declares Gradle 9+ while the wrapper is still 8.10.2, which may break local or release publish tasks until Gradle is upgraded.

Overview
Updates the com.vanniktech.maven.publish Gradle plugin version in build.gradle from 0.30.0 to 0.37.0, with no other build or mavenPublishing DSL changes.

That upgrade pulls in newer Maven Central publishing behavior (for example, different default checksum files and deployment validation in recent releases). CI and release flows that run ./gradlew test, publishToMavenLocal, or publishAndReleaseToMavenCentral will use the new plugin semantics on the next Gradle invocation.

^{Reviewed by Cursor Bugbot for commit e735d8b. Bugbot is set up for automated code reviews on this repo. Configure here.}