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.26.0 #1249

Merged
merged 2 commits into from
Jan 4, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 4, 2024

Mend Renovate

This PR contains the following updates:

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

Release Notes

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

v0.26.0

Compare Source

  • It's now supported to call configure(Platform) from the main plugin to modify
    what is getting published. Check out the docs for more details
  • The base plugin now has a configureBasedOnAppliedPlugins DSL method to
    allow applying the default configure logic of the main plugin.
  • Calling configure(Platform) now validates that the required plugins are
    applied (e.g. Android Gradle Plugin for Android projects).
  • It's now possible to disable source publishing for KMP projects.
  • Fixed an issue which would cause the javadoc jar task to be registered multiple
    times for Gradle plugin projects with more than one publication. Thanks to
    @​autonomousapps for the fix.
  • Publishing Kotlin/JS projects has been deprecated and will be removed in the
    next release, because the Kotlin/JS plugin has been deprecated.
  • The internal task to create a javadoc jar for certain project types has been renamed
    from simpleJavadocJar to plainJavadocJar. Thanks to @​sschuberth.
Minimum supported versions
  • JDK 11
  • Gradle 7.6
  • Android Gradle Plugin 7.4.0
  • Kotlin Gradle Plugin 1.8.20
Compatibility tested up to
  • JDK 21
  • Gradle 8.5
  • Android Gradle Plugin 8.2.0
  • Android Gradle Plugin 8.3.0-alpha17
  • Kotlin Gradle Plugin 1.9.21
  • Kotlin Gradle Plugin 2.0.0-Beta1
Configuration cache status

When using Gradle 8.1 or newer configuration cache is generally supported.

Exceptions to that are:

  • 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from RBusarow as a code owner January 4, 2024 13:56
@renovate renovate bot added automerge dependencies Pull requests that update a dependency file labels Jan 4, 2024
Copy link
Contributor Author

renovate bot commented Jan 4, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@kodiakhq kodiakhq bot merged commit addc9e6 into main Jan 4, 2024
49 checks passed
@kodiakhq kodiakhq bot deleted the renovate/vanniktech.publish branch January 4, 2024 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant