Skip to content

Comments

Update plugin maven-publish to v0.36.0#198

Merged
cedrickcooke merged 1 commit intomainfrom
renovate/com.vanniktech.maven.publish-0.x
Jan 26, 2026
Merged

Update plugin maven-publish to v0.36.0#198
cedrickcooke merged 1 commit intomainfrom
renovate/com.vanniktech.maven.publish-0.x

Conversation

@juul-mobile-bot
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
com.vanniktech.maven.publish plugin minor 0.35.00.36.0

Release Notes

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

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

Configuration

📅 Schedule: 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 has been generated by Renovate Bot.

@cedrickcooke cedrickcooke enabled auto-merge (squash) January 23, 2026 17:29
@juul-mobile-bot juul-mobile-bot force-pushed the renovate/com.vanniktech.maven.publish-0.x branch from 5c7d9d5 to 2eef9bc Compare January 26, 2026 09:43
@cedrickcooke cedrickcooke merged commit 3c10417 into main Jan 26, 2026
5 checks passed
@cedrickcooke cedrickcooke deleted the renovate/com.vanniktech.maven.publish-0.x branch January 26, 2026 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants