Skip to content
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

Update dependency com.vanniktech:gradle-maven-publish-plugin to v0.30.0 - autoclosed #131

Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 21, 2024

This PR contains the following updates:

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

Release Notes

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

v0.30.0

Compare Source

  • Add support for Dokka 2.0.0-Beta
    • Supports org.jetbrains.dokka.experimental.gradle.pluginMode=V2Enabled
    • Supports both org.jetbrains.dokka and org.jetbrains.dokka-javadoc
    • If both are applied the javadoc output is published
    • Removed support for the old org.jetbrains.dokka-android plugin
  • Support custom Sonatype hosts by providing a https url in SONATYPE_HOST Gradle property
  • Remove usages of deprecated Gradle API that is scheduled to be removed in Gradle 9.0
  • Raised minimum supported Gradle version
  • Improve naming of javadoc jars
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.10.2
  • Android Gradle Plugin 8.7.0
  • Android Gradle Plugin 8.8.0-alpha05
  • Kotlin Gradle Plugin 2.0.20
  • Kotlin Gradle Plugin 2.1.0-Beta1
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.29.0

Compare Source

  • Added configureBasedOnAppliedPlugins(sourcesJar: Boolean, javadocJar: Boolean)
    overload that allows disabling sources and javadoc jars without having to use
    the more granular Platform APIs.
  • For Java library and Kotlin/JVM projects the Gradle module metadata now properly
    includes the sources jar.
  • When running on Gradle 8.8 or newer the pom configuration is not applied in
    afterEvaluate anymore, making manual overrides easier.
  • Fix potential issue with the javadoc jar tasks that can cause Gradle to disable
    optimizations.
  • When staging profiles can't be loaded the status code of the response is added
    to the error message.
Minimum supported versions
  • JDK 11
  • Gradle 8.1
  • Android Gradle Plugin 8.0.0
  • Kotlin Gradle Plugin 1.9.20
Compatibility tested up to
  • JDK 21
  • Gradle 8.8
  • Android Gradle Plugin 8.5.0
  • Android Gradle Plugin 8.6.0-alpha06
  • Kotlin Gradle Plugin 2.0.0
  • Kotlin Gradle Plugin 2.0.20-Beta1
Configuration cache status

Configuration cache is generally supported, except for:

  • Publishing releases to Maven Central (snapshots are fine), blocked by Gradle issue #​22779.
  • Dokka does not support configuration cache

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/com.vanniktech-gradle-maven-publish-plugin-0.x branch from 9688657 to a508987 Compare July 16, 2024 15:35
@renovate renovate bot force-pushed the renovate/com.vanniktech-gradle-maven-publish-plugin-0.x branch from a508987 to 634fda4 Compare August 9, 2024 02:42
@renovate renovate bot force-pushed the renovate/com.vanniktech-gradle-maven-publish-plugin-0.x branch from 634fda4 to 1f29a68 Compare August 29, 2024 19:53
@renovate renovate bot changed the title Update dependency com.vanniktech:gradle-maven-publish-plugin to v0.29.0 Update dependency com.vanniktech:gradle-maven-publish-plugin to v0.30.0 Oct 13, 2024
@renovate renovate bot force-pushed the renovate/com.vanniktech-gradle-maven-publish-plugin-0.x branch from 1f29a68 to d7b5ffd Compare October 13, 2024 13:56
@renovate renovate bot force-pushed the renovate/com.vanniktech-gradle-maven-publish-plugin-0.x branch from d7b5ffd to 7f897da Compare October 30, 2024 17:43
@renovate renovate bot force-pushed the renovate/com.vanniktech-gradle-maven-publish-plugin-0.x branch from 7f897da to ec9f1f5 Compare October 31, 2024 20:53
@mattprecious mattprecious merged commit 3c4992e into main Nov 11, 2024
1 check passed
@mattprecious mattprecious deleted the renovate/com.vanniktech-gradle-maven-publish-plugin-0.x branch November 11, 2024 21:44
@renovate renovate bot changed the title Update dependency com.vanniktech:gradle-maven-publish-plugin to v0.30.0 Update dependency com.vanniktech:gradle-maven-publish-plugin to v0.30.0 - autoclosed Nov 11, 2024
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