Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 17, 2025

This PR contains the following updates:

Package Change Age Confidence
com.vanniktech.maven.publish 0.30.0 -> 0.34.0 age confidence

Release Notes

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

v0.34.0

Compare Source

  • Added configuration cache support for publishing.
  • Removed support for publishing through Sonatype OSSRH since it has been shut down. See the
    0.33.0 release notes for upgrade
    instructions if you haven't upgraded yet.
    • SonatypeHost has been removed from the DSL.
    • SONATYPE_HOST only supports CENTRAL_PORTAL now. It's recommended to use the following properties instead:
      • mavenCentralPublishing=true replaces SONATYPE_HOST=CENTRAL_PORTAL.
      • mavenCentralAutomaticPublishing=true replaces SONATYPE_AUTOMATIC_RELEASE=true.
  • Update the Central Portal Publisher APIs to the latest.
  • It's now possible to mix SNAPSHOT versions and release versions when running publish tasks.
  • Fixed Gradle's deprecation warning caused by invalid URI.
  • Fixed check for the minimum supported Gradle version running too late in some cases.

Thanks to @​Goooler and @​solrudev for their contributions to this release.

Minimum supported versions
  • JDK 11
  • Gradle 8.5
  • Android Gradle Plugin 8.0.0
  • Kotlin Gradle Plugin 1.9.20
Compatibility tested up to
  • JDK 24
  • Gradle 8.14.3
  • Gradle 9.0.0-rc2
  • Android Gradle Plugin 8.11.1
  • Android Gradle Plugin 8.12.0-alpha08
  • Kotlin Gradle Plugin 2.2.0
  • Kotlin Gradle Plugin 2.2.20-Beta1

v0.33.0

Compare Source

[!CAUTION]
Sonatype OSSRH (oss.sonatype.org and s01.oss.sonatype.org) will be shut down on June 30, 2025.

Migration steps:

  1. Sign in to the Central Portal with your existing Sonatype account.
  2. Go to Namespaces and click "Migrate Namespace"
    for the relevant namespace. Confirm the migration and wait for it to complete.
  3. Optional: If you want to publish snapshots of your project tap the 3 dots next to your namespace and
    select "Enable SNAPSHOTs".
  4. Go to Account and select "Generate User Token". Use the shown
    "Username" and "Password" as values for mavenCentralUsername and mavenCentralPassword.
  5. Configure this plugin to publish to Central Portal. Either update your SONATYPE_HOST property from
    DEFAULT or S01 to CENTRAL_PORTAL or call publishToMavenCentral()/publishToMavenCentral(automaticRelease)
    without a SonatypeHost parameter.

BREAKING

  • publishToMavenCentral() and publishToMavenCentral(automaticRelease) without SonatypeHost will
    now publish through the Central Portal.
  • Deprecated overloads of publishToMavenCentral that take a SonatypeHost parameter.
  • Deprecated SonatypeHost.

New

  • Basic experimental support for com.android.fused-library. There are currently several limitations
    on the Android Gradle plugin side which make signing as well as publishing sources/javadocs not possible.

Improvements

  • Added new Gradle properties:
    • mavenCentralPublishing=true replaces SONATYPE_HOST=CENTRAL_PORTAL.
    • mavenCentralAutomaticPublishing=true replaces SONATYPE_AUTOMATIC_RELEASE=true.
    • signAllPublications=true replaces RELEASE_SIGNING_ENABLED=true.
    • Note: The old properties continue to work and there are no plans to remove them.
  • The base plugin is now compatible with isolated projects as long as pomFromGradleProperties() is not called.
  • It's possible to pass a TaskProvider to JavadocJar.Dokka.
  • Improved naming of produced -javadoc jars (locally, the name of the published artifact is unchanged).
  • Resolve issue that caused version to be read too early when publishing to Central Portal.

Thanks to @​Goooler, @​solrudev and @​sschuberth for their contributions to this release.

Minimum supported versions
  • JDK 11
  • Gradle 8.5
  • Android Gradle Plugin 8.0.0
  • Kotlin Gradle Plugin 1.9.20
Compatibility tested up to
  • JDK 24
  • Gradle 8.14.2
  • Gradle 9.0-rc1
  • Android Gradle Plugin 8.10.0
  • Android Gradle Plugin 8.11.0-rc02
  • Android Gradle Plugin 8.12.0-alpha06
  • Kotlin Gradle Plugin 2.1.21
  • Kotlin Gradle Plugin 2.2.0-RC3

v0.32.0

Compare Source

  • Improve names of Central Portal deployments.
  • Fix an issue where the wrong staging profile for (s01.)oss.sonatype.org was selected when publishing to Maven Central.
  • Fix incompatibility with Kotlin 1.9.x when used through compiled plugins.
  • Improve error message when not being able to detect Kotlin plugin.
  • Fix an issue with detecting whether configuration cache is enabled which lead to a not actionable error message.
  • Fix compatibility with Gradle 9.0.
Minimum supported versions
  • JDK 11
  • Gradle 8.5
  • Android Gradle Plugin 8.0.0
  • Kotlin Gradle Plugin 1.9.20
Compatibility tested up to
  • JDK 24
  • Gradle 8.14
  • Gradle 9.0-milestone-6
  • Android Gradle Plugin 8.10.0
  • Android Gradle Plugin 8.11.0-alpha10
  • Kotlin Gradle Plugin 2.1.20
  • Kotlin Gradle Plugin 2.1.21-RC2
  • Kotlin Gradle Plugin 2.2.0-Beta2
Configuration cache status

Configuration cache is generally supported, except for:

  • Publishing releases to Maven Central (snapshots are fine), blocked by Gradle issue #​22779.
  • When using Dokka 1.x or Dokka 2.x without V2Enabled.

v0.31.0

Compare Source

  • Add support for publishing snapshots to Central Portal.
    • Make sure to enable snapshots for your namespace on central.sonatype.com.
    • Thanks to @​solrudev for the contribution.
  • Add support for multiple matching staging profiles by taking the one with the longest matching prefix.
Minimum supported versions
  • JDK 11
  • Gradle 8.5
  • Android Gradle Plugin 8.0.0
  • Kotlin Gradle Plugin 1.9.20
Compatibility tested up to
  • JDK 23
  • Gradle 8.13
  • Android Gradle Plugin 8.9.0
  • Android Gradle Plugin 8.10.0-alpha07
  • Kotlin Gradle Plugin 2.1.10
  • Kotlin Gradle Plugin 2.1.20-RC
Configuration cache status

Configuration cache is generally supported, except for:

  • Publishing releases to Maven Central (snapshots are fine), blocked by Gradle issue #​22779.
  • When using Dokka 1.x or Dokka 2.x without V2Enabled.

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title chore(deps): update plugin com.vanniktech.maven.publish to v0.31.0 chore(deps): update plugin com.vanniktech.maven.publish to v0.32.0 May 14, 2025
@renovate renovate bot force-pushed the renovate/com.vanniktech.maven.publish-0.x branch from bc8dd8b to c56f204 Compare May 14, 2025 17:26
@renovate renovate bot force-pushed the renovate/com.vanniktech.maven.publish-0.x branch from c56f204 to 49fd8e3 Compare June 22, 2025 18:29
@renovate renovate bot changed the title chore(deps): update plugin com.vanniktech.maven.publish to v0.32.0 chore(deps): update plugin com.vanniktech.maven.publish to v0.33.0 Jun 22, 2025
@renovate renovate bot changed the title chore(deps): update plugin com.vanniktech.maven.publish to v0.33.0 chore(deps): update plugin com.vanniktech.maven.publish to v0.34.0 Jul 14, 2025
@renovate renovate bot force-pushed the renovate/com.vanniktech.maven.publish-0.x branch from 49fd8e3 to 77d13bb Compare July 14, 2025 14:05
@renovate renovate bot force-pushed the renovate/com.vanniktech.maven.publish-0.x branch from 77d13bb to e57c4c3 Compare September 8, 2025 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants