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

chore(deps): update plugin com.vanniktech.maven.publish.base to v0.29.0 #128

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 18, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.vanniktech.maven.publish.base 0.27.0 -> 0.29.0 age adoption passing confidence

Release Notes

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

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

v0.28.0

Compare Source

  • Added support for publishing through the new Central Portal. To use
    this use the CENTRAL_PORTAL option when specifying the Sonatype host.
  • For Kotlin Multiplatform the main plugin will now automatically publish the
    release variant if the project has an Android target and no variant was explicitly
    specified through the Kotlin Gradle DSL.
  • Support specifying the Android variants to publish in KotlinMultiplatform(...).
  • Updated minimum supported Gradle, Android Gradle Plugin and Kotlin versions.
  • Removed support for the deprecated Kotlin/JS plugin.
  • Removed the deprecated closeAndReleaseRepository task. Use releaseRepository, which
    is functionally equivalent, instead.
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.6
  • Gradle 8.7-rc-3
  • Android Gradle Plugin 8.3.0
  • Android Gradle Plugin 8.4.0-alpha13
  • Kotlin Gradle Plugin 1.9.23
  • Kotlin Gradle Plugin 2.0.0-Beta4
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 - "before 4am on Monday" (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.base to v0.28.0 chore(deps): update plugin com.vanniktech.maven.publish.base to v0.29.0 Jun 21, 2024
@renovate renovate bot force-pushed the renovate/com.vanniktech.maven.publish.base-0.x branch from ffbaffb to 213d4a2 Compare June 21, 2024 11:39
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