Skip to content

Update dependency com.vanniktech:gradle-maven-publish-plugin to v0.33.0 #213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 22, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.vanniktech:gradle-maven-publish-plugin 0.32.0 -> 0.33.0 age adoption passing confidence

Release Notes

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

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

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 is behind base branch, 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.

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.

0 participants