Bump com.vanniktech.maven.publish:com.vanniktech.maven.publish.gradle.plugin from 0.35.0 to 0.36.0 in the non-breaking-changes group #321

Merged
dependabot[bot] merged 1 commit from dependabot/gradle/non-breaking-changes-4346d2fac3 into main 2026-01-19 19:45:47 +01:00
dependabot[bot] commented 2026-01-19 17:16:17 +01:00 (Migrated from github.com)

Bumps the non-breaking-changes group with 1 update: com.vanniktech.maven.publish:com.vanniktech.maven.publish.gradle.plugin.

Updates com.vanniktech.maven.publish:com.vanniktech.maven.publish.gradle.plugin from 0.35.0 to 0.36.0

Release notes

Sourced from com.vanniktech.maven.publish:com.vanniktech.maven.publish.gradle.plugin'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:com.vanniktech.maven.publish.gradle.plugin'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
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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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 the non-breaking-changes group with 1 update: [com.vanniktech.maven.publish:com.vanniktech.maven.publish.gradle.plugin](https://github.com/vanniktech/gradle-maven-publish-plugin). Updates `com.vanniktech.maven.publish:com.vanniktech.maven.publish.gradle.plugin` from 0.35.0 to 0.36.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/releases">com.vanniktech.maven.publish:com.vanniktech.maven.publish.gradle.plugin's releases</a>.</em></p> <blockquote> <h2>0.36.0</h2> <p><strong>BREAKING</strong></p> <ul> <li>Updated minimum supported JDK, Gradle, Android Gradle Plugin and Kotlin versions.</li> <li>Removed support for Dokka v1, it's now required to use Dokka in v2 mode.</li> <li>Mark <code>DirectorySignatureType</code> internal.</li> </ul> <p><strong>Behavior changes</strong></p> <ul> <li><code>validateDeployment</code> now has the <code>DeploymentValidation</code> enum as type instead of being a boolean. The default is now to just wait for the <code>VALIDATED</code> state. The previous behavior can be achieved by setting it to <code>PUBLISHED</code>. <code>NONE</code> can be used for disabling the validation completely.</li> <li>When calling <code>configure(...)</code> manually to configure what to publish and not passing <code>javadocJar</code> explicity, the plugin now defaults to publishing an empty javadoc jar.</li> </ul> <p><strong>Features</strong></p> <ul> <li>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.</li> <li>Added consistent <code>JavadocJar</code> and <code>SourcesJar</code> options to <code>configureBasedOnAppliedPlugins</code> and to all applicable project types that can be passed to <code>configure</code>. The previous <code>Boolean</code> based versions have been deprecated.</li> <li>When enabling Maven Central publishing through the DSL, the <code>mavenCentralDeploymentValidation</code> and <code>mavenCentralAutomaticPublishing</code> 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.</li> <li>When isolated projects is enabled the module/project specific <code>gradle.properties</code> files are now considered in the same way they are when isolated projects is disabled.</li> </ul> <p><strong>Improvements</strong></p> <ul> <li>Better error message when Maven Central credentials are missing.</li> </ul> <h4>Minimum supported versions</h4> <ul> <li>JDK 17</li> <li>Gradle 9.0.0</li> <li>Android Gradle Plugin 8.13.0</li> <li>Kotlin Gradle Plugin 2.2.0</li> </ul> <h4>Compatibility tested up to</h4> <ul> <li>JDK 25</li> <li>Gradle 9.3.0</li> <li>Gradle 9.4.0-milestone-4</li> <li>Android Gradle Plugin 8.13.2</li> <li>Android Gradle Plugin 9.0.0</li> <li>Android Gradle Plugin 9.1.0-alpha05</li> <li>Kotlin Gradle Plugin 2.3.0</li> <li>Kotlin Gradle Plugin 2.3.20-Beta1</li> </ul> <h2>0.36.0-rc2</h2> <p><strong>BREAKING</strong></p> <ul> <li>Updated minimum supported JDK, Gradle, Android Gradle Plugin and Kotlin versions.</li> <li>Removed support for Dokka v1, it's now required to use Dokka in v2 mode.</li> <li>Mark <code>DirectorySignatureType</code> internal.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/blob/main/CHANGELOG.md">com.vanniktech.maven.publish:com.vanniktech.maven.publish.gradle.plugin's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/releases/tag/0.36.0">0.36.0</a> <em>(2026-01-13)</em></h2> <p><strong>BREAKING</strong></p> <ul> <li>Updated minimum supported JDK, Gradle, Android Gradle Plugin and Kotlin versions.</li> <li>Removed support for Dokka v1, it's now required to use Dokka in v2 mode.</li> <li>Mark <code>DirectorySignatureType</code> internal.</li> </ul> <p><strong>Behavior changes</strong></p> <ul> <li><code>validateDeployment</code> now has the <code>DeploymentValidation</code> enum as type instead of being a boolean. The default is now to just wait for the <code>VALIDATED</code> state. The previous behavior can be achieved by setting it to <code>PUBLISHED</code>. <code>NONE</code> can be used for disabling the validation completely.</li> <li>When calling <code>configure(...)</code> manually to configure what to publish and not passing <code>javadocJar</code> explicity, the plugin now defaults to publishing an empty javadoc jar.</li> </ul> <p><strong>Features</strong></p> <ul> <li>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.</li> <li>Added consistent <code>JavadocJar</code> and <code>SourcesJar</code> options to <code>configureBasedOnAppliedPlugins</code> and to all applicable project types that can be passed to <code>configure</code>. The previous <code>Boolean</code> based versions have been deprecated.</li> <li>When enabling Maven Central publishing through the DSL, the <code>mavenCentralDeploymentValidation</code> and <code>mavenCentralAutomaticPublishing</code> 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.</li> <li>When isolated projects is enabled the module/project specific <code>gradle.properties</code> files are now considered in the same way they are when isolated projects is disabled.</li> </ul> <p><strong>Improvements</strong></p> <ul> <li>Better error message when Maven Central credentials are missing.</li> </ul> <h4>Minimum supported versions</h4> <ul> <li>JDK 17</li> <li>Gradle 9.0.0</li> <li>Android Gradle Plugin 8.13.0</li> <li>Kotlin Gradle Plugin 2.2.0</li> </ul> <h4>Compatibility tested up to</h4> <ul> <li>JDK 25</li> <li>Gradle 9.3.0</li> <li>Gradle 9.4.0-milestone-4</li> <li>Android Gradle Plugin 8.13.2</li> <li>Android Gradle Plugin 9.0.0</li> <li>Android Gradle Plugin 9.1.0-alpha05</li> <li>Kotlin Gradle Plugin 2.3.0</li> <li>Kotlin Gradle Plugin 2.3.20-Beta1</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/0a5fa58778e382151c7502535ada88777b1ad416"><code>0a5fa58</code></a> rc2 and wait for published</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/695e18a932a80cd09116591e7f6245988e71f6c4"><code>695e18a</code></a> rc1</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/f92dc3a37bd7dad8189699603d90b024946388d7"><code>f92dc3a</code></a> Changelog for 0.36.0</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/bddd1e6d7bb331b00f17d579a0d5daf1a8ebcba5"><code>bddd1e6</code></a> Update dependency org.jetbrains.kotlin.jvm to v2.3.20-Beta1 (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/1289">#1289</a>)</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/22f90b2df58a36b726bb44286ca24d696d3acd5c"><code>22f90b2</code></a> Update Gradle to v9.3.0 (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/1301">#1301</a>)</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/d7d5f3430181ec0b50ee64ce7f1ffce7ccd9ed25"><code>d7d5f34</code></a> Update android.gradle to v9 (major) (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/1298">#1298</a>)</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/3d262a6a4742a745481aaca7a2343a1bd342de28"><code>3d262a6</code></a> Update dependency com.android.library to v9.1.0-alpha05 (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/1300">#1300</a>)</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/a8573eda99520a67786371d56aeba11628e8db01"><code>a8573ed</code></a> Update plugin com.gradle.develocity to v4.3.1 (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/1299">#1299</a>)</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/ee0f2e3bba836ab4122256537f3cc8eab89b161b"><code>ee0f2e3</code></a> Fix typo in default <code>DeploymentValidation</code> and correct documentation (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/1296">#1296</a>)</li> <li><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/commit/783599f03ed9be842f67897dc03750ef4cc57a4d"><code>783599f</code></a> Update dependency com.android.library to v9.0.0 (<a href="https://redirect.github.com/vanniktech/gradle-maven-publish-plugin/issues/1297">#1297</a>)</li> <li>Additional commits viewable in <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/compare/0.35.0...0.36.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.vanniktech.maven.publish:com.vanniktech.maven.publish.gradle.plugin&package-manager=gradle&previous-version=0.35.0&new-version=0.36.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@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 </details>
Sign in to join this conversation.
No description provided.