chore: bump com.vanniktech:gradle-maven-publish-plugin in / by dependabot[bot] · Pull Request #828 · mParticle/mparticle-android-sdk

dependabot · 2026-09-18T22:50:06Z

Bumps com.vanniktech:gradle-maven-publish-plugin in / from 0.31.0 to 0.37.0.

Updates com.vanniktech:gradle-maven-publish-plugin from 0.31.0 to 0.37.0

Release notes

Sourced from com.vanniktech:gradle-maven-publish-plugin'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:gradle-maven-publish-plugin'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

Updates com.vanniktech:gradle-maven-publish-plugin from 0.31.0 to 0.37.0

Release notes

Sourced from com.vanniktech:gradle-maven-publish-plugin'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:gradle-maven-publish-plugin'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

Updates com.vanniktech:gradle-maven-publish-plugin from 0.31.0 to 0.37.0

Release notes

Sourced from com.vanniktech:gradle-maven-publish-plugin'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:gradle-maven-publish-plugin'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

Updates com.vanniktech:gradle-maven-publish-plugin from 0.31.0 to 0.37.0

Release notes

Sourced from com.vanniktech:gradle-maven-publish-plugin'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:gradle-maven-publish-plugin'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

Updates com.vanniktech:gradle-maven-publish-plugin from 0.31.0 to 0.37.0

Release notes

Sourced from com.vanniktech:gradle-maven-publish-plugin'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:gradle-maven-publish-plugin'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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps [com.vanniktech:gradle-maven-publish-plugin](https://github.com/vanniktech/gradle-maven-publish-plugin) in `/` from 0.31.0 to 0.37.0. Updates `com.vanniktech:gradle-maven-publish-plugin` from 0.31.0 to 0.37.0 - [Release notes](https://github.com/vanniktech/gradle-maven-publish-plugin/releases) - [Changelog](https://github.com/vanniktech/gradle-maven-publish-plugin/blob/main/CHANGELOG.md) - [Commits](vanniktech/gradle-maven-publish-plugin@0.31.0...0.37.0) Updates `com.vanniktech:gradle-maven-publish-plugin` from 0.31.0 to 0.37.0 - [Release notes](https://github.com/vanniktech/gradle-maven-publish-plugin/releases) - [Changelog](https://github.com/vanniktech/gradle-maven-publish-plugin/blob/main/CHANGELOG.md) - [Commits](vanniktech/gradle-maven-publish-plugin@0.31.0...0.37.0) Updates `com.vanniktech:gradle-maven-publish-plugin` from 0.31.0 to 0.37.0 - [Release notes](https://github.com/vanniktech/gradle-maven-publish-plugin/releases) - [Changelog](https://github.com/vanniktech/gradle-maven-publish-plugin/blob/main/CHANGELOG.md) - [Commits](vanniktech/gradle-maven-publish-plugin@0.31.0...0.37.0) Updates `com.vanniktech:gradle-maven-publish-plugin` from 0.31.0 to 0.37.0 - [Release notes](https://github.com/vanniktech/gradle-maven-publish-plugin/releases) - [Changelog](https://github.com/vanniktech/gradle-maven-publish-plugin/blob/main/CHANGELOG.md) - [Commits](vanniktech/gradle-maven-publish-plugin@0.31.0...0.37.0) Updates `com.vanniktech:gradle-maven-publish-plugin` from 0.31.0 to 0.37.0 - [Release notes](https://github.com/vanniktech/gradle-maven-publish-plugin/releases) - [Changelog](https://github.com/vanniktech/gradle-maven-publish-plugin/blob/main/CHANGELOG.md) - [Commits](vanniktech/gradle-maven-publish-plugin@0.31.0...0.37.0) --- updated-dependencies: - dependency-name: com.vanniktech:gradle-maven-publish-plugin dependency-version: 0.37.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: gradle - dependency-name: com.vanniktech:gradle-maven-publish-plugin dependency-version: 0.37.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: gradle - dependency-name: com.vanniktech:gradle-maven-publish-plugin dependency-version: 0.37.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: gradle - dependency-name: com.vanniktech:gradle-maven-publish-plugin dependency-version: 0.37.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: gradle - dependency-name: com.vanniktech:gradle-maven-publish-plugin dependency-version: 0.37.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: gradle ... Signed-off-by: dependabot[bot] <support@github.com>

cursor · 2026-09-18T22:50:11Z

PR Summary

Low Risk
Low risk build configuration update with no changes to runtime application code.

Overview
Updates the gradle-maven-publish-plugin build dependency in build-logic/build.gradle.kts from version 0.31.0 to 0.37.0.

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

cursor

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

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 4f6070c. Configure here.}

cursor · 2026-09-18T22:52:08Z


 dependencies {
-    implementation("com.vanniktech:gradle-maven-publish-plugin:0.31.0")
+    implementation("com.vanniktech:gradle-maven-publish-plugin:0.37.0")


Plugin requires Gradle 9.0 but project uses 8.5

High Severity

gradle-maven-publish-plugin 0.37.0 requires a minimum Gradle version of 9.0.0, but gradle/wrapper/gradle-wrapper.properties specifies gradle-8.5-bin.zip. This version mismatch will cause the build to fail at plugin resolution or configuration time, breaking all publish-related tasks.

^{Reviewed by Cursor Bugbot for commit 4f6070c. Configure here.}

github-actions · 2026-09-18T22:52:19Z

📦 SDK Size Impact Report

What the SDK adds to a minified release APK.

Measured against an empty baseline app. Unlike the Rokt kit, android-core ships no Compose and no resources, so there is nothing here that a host app would already provide.

mParticle Core SDK

Metric	Target branch	This PR	Change
APK size	119.76 KB	not measured	not measured
Download size	117.58 KB	not measured	not measured
Dex bytes	213.75 KB	not measured	not measured

ℹ️ Size could not be measured on one or both branches.

Raw measurements

Target branch:

{"baseline_dex_bytes": 0, "baseline_download_bytes": 2511, "baseline_install_bytes": 7528, "core_dex_bytes": 218884, "core_download_bytes": 122911, "core_install_bytes": 130162}

This PR:

not measured

_{Measured 4f6070c merged into 31bc319}

github-actions · 2026-09-18T23:00:29Z

📦 SDK Size Impact Report

What the SDK adds to a minified release APK.

Measured against a Compose + Material3 reference app, so these are the costs on top of an app that already ships Compose. The reference app's dependencies are a documented convention, not a measured average: see size-report-rokt/README.md.

mParticle Core + Rokt kit

Metric	Target branch	This PR	Change
APK size	1.31 MB	not measured	not measured
Download size	1.29 MB	not measured	not measured
Dex bytes	2.33 MB	not measured	not measured

Rokt SDK+ umbrella (adds the payment extension)

Metric	Target branch	This PR	Change	On top of mParticle Core + Rokt kit
APK size	6.55 MB	not measured	not measured	not measured
Download size	6.44 MB	not measured	not measured	not measured
Dex bytes	7.13 MB	not measured	not measured	not measured

ℹ️ Size could not be measured on one or both branches.

Raw measurements

Target branch:

{"baseline_dex_bytes": 1829108, "baseline_download_bytes": 1240062, "baseline_install_bytes": 1300934, "kit_dex_bytes": 4274892, "kit_download_bytes": 2596899, "kit_install_bytes": 2674686, "sdkplus_dex_bytes": 9305380, "sdkplus_download_bytes": 7989544, "sdkplus_install_bytes": 8165359}

This PR:

not measured

_{Measured 4f6070c merged into 31bc319}

thomson-t · 2026-09-21T13:14:20Z

Not compatible now. Will update in the future after gradle version update

dependabot · 2026-09-21T13:14:22Z

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

dependabot Bot added the dependabot label Sep 18, 2026

dependabot Bot requested a review from a team as a code owner September 18, 2026 22:50

dependabot Bot added the dependabot label Sep 18, 2026

cursor Bot reviewed Sep 18, 2026

View reviewed changes

thomson-t closed this Sep 21, 2026

dependabot Bot deleted the dependabot/gradle/gradle-93da4f6457 branch September 21, 2026 13:14

Navigation Menu

chore: bump com.vanniktech:gradle-maven-publish-plugin in / - #828

chore: bump com.vanniktech:gradle-maven-publish-plugin in /#828
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/gradle/gradle-93da4f6457

dependabot Bot commented on behalf of github Sep 18, 2026

Uh oh!

cursor Bot commented Sep 18, 2026 •

edited

Loading

Uh oh!

cursor Bot left a comment

Uh oh!

cursor Bot Sep 18, 2026

Uh oh!

github-actions Bot commented Sep 18, 2026

Uh oh!

github-actions Bot commented Sep 18, 2026

Uh oh!

thomson-t commented Sep 21, 2026

Uh oh!

dependabot Bot commented on behalf of github Sep 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

dependabot Bot commented on behalf of github Sep 18, 2026

0.37.0

Minimum supported versions

Compatibility tested up to

0.37.0-rc1

Minimum supported versions

Compatibility tested up to

0.36.0

0.37.0 (2026-06-21)

Minimum supported versions

Compatibility tested up to

0.36.0 (2026-01-13)

0.37.0

Minimum supported versions

Compatibility tested up to

0.37.0-rc1

Minimum supported versions

Compatibility tested up to

0.36.0

0.37.0 (2026-06-21)

Minimum supported versions

Compatibility tested up to

0.36.0 (2026-01-13)

0.37.0

Minimum supported versions

Compatibility tested up to

0.37.0-rc1

Minimum supported versions

Compatibility tested up to

0.36.0

0.37.0 (2026-06-21)

Minimum supported versions

Compatibility tested up to

0.36.0 (2026-01-13)

0.37.0

Minimum supported versions

Compatibility tested up to

0.37.0-rc1

Minimum supported versions

Compatibility tested up to

0.36.0

0.37.0 (2026-06-21)

Minimum supported versions

Compatibility tested up to

0.36.0 (2026-01-13)

0.37.0

Minimum supported versions

Compatibility tested up to

0.37.0-rc1

Minimum supported versions

Compatibility tested up to

0.36.0

0.37.0 (2026-06-21)

Minimum supported versions

Compatibility tested up to

0.36.0 (2026-01-13)

Uh oh!

cursor Bot commented Sep 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Summary

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor Bot Sep 18, 2026

Choose a reason for hiding this comment

Plugin requires Gradle 9.0 but project uses 8.5

Uh oh!

github-actions Bot commented Sep 18, 2026

📦 SDK Size Impact Report

mParticle Core SDK

Uh oh!

github-actions Bot commented Sep 18, 2026

📦 SDK Size Impact Report

mParticle Core + Rokt kit

Rokt SDK+ umbrella (adds the payment extension)

Uh oh!

thomson-t commented Sep 21, 2026

Uh oh!

cursor Bot commented Sep 18, 2026 •

edited

Loading