Skip to content

build(deps): bump com.vanniktech.maven.publish from 0.32.0 to 0.36.0#140

Merged
kirich1409 merged 5 commits intomainfrom
dependabot/gradle/com.vanniktech.maven.publish-0.36.0
Mar 23, 2026
Merged

build(deps): bump com.vanniktech.maven.publish from 0.32.0 to 0.36.0#140
kirich1409 merged 5 commits intomainfrom
dependabot/gradle/com.vanniktech.maven.publish-0.36.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 23, 2026

Bumps com.vanniktech.maven.publish from 0.32.0 to 0.36.0.

Release notes

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

0.36.0

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

0.36.0-rc2

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.

... (truncated)

Changelog

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

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

0.35.0 (2025-11-11)

  • Add support for publishing Kotlin Multiplatform libraries that use com.android.kotlin.multiplatform.library.
  • Add support for validating deployments to Central Portal

... (truncated)

Commits

Dependabot compatibility score

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)

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 23, 2026

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

dependabot bot and others added 5 commits March 23, 2026 16:12
Bumps [com.vanniktech.maven.publish](https://github.com/vanniktech/gradle-maven-publish-plugin) from 0.32.0 to 0.36.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.32.0...0.36.0)

---
updated-dependencies:
- dependency-name: com.vanniktech.maven.publish
  dependency-version: 0.36.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
SonatypeHost enum was removed in 0.36.0; CENTRAL_PORTAL is now
the default host so no argument is needed.
…lish 0.36.0

Module was added to main after the dependabot branch was cut; merge
brought in the old SonatypeHost.CENTRAL_PORTAL call which was removed
in 0.36.0.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Dokka v2 replaces `dokkaHtmlMultiModule` with `dokkaGenerate` and
outputs to `build/dokka/html/` instead of `build/dokka/htmlMultiModule/`.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@kirich1409 kirich1409 force-pushed the dependabot/gradle/com.vanniktech.maven.publish-0.36.0 branch from 068f592 to 6d54159 Compare March 23, 2026 13:12
@kirich1409 kirich1409 merged commit ffb05ab into main Mar 23, 2026
8 of 9 checks passed
@dependabot dependabot bot deleted the dependabot/gradle/com.vanniktech.maven.publish-0.36.0 branch March 23, 2026 13:27
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