chore(deps): update plugin mavenpublish to v0.29.0 #130
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.25.3
->0.29.0
Release Notes
vanniktech/gradle-maven-publish-plugin (com.vanniktech.maven.publish)
v0.29.0
Compare Source
configureBasedOnAppliedPlugins(sourcesJar: Boolean, javadocJar: Boolean)
overload that allows disabling sources and javadoc jars without having to use
the more granular
Platform
APIs.includes the sources jar.
afterEvaluate
anymore, making manual overrides easier.optimizations.
to the error message.
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
v0.28.0
Compare Source
this use the
CENTRAL_PORTAL
option when specifying the Sonatype host.release
variant if the project has an Android target and no variant was explicitlyspecified through the Kotlin Gradle DSL.
KotlinMultiplatform(...)
.closeAndReleaseRepository
task. UsereleaseRepository
, whichis functionally equivalent, instead.
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
v0.27.0
Compare Source
releaseRepository
releases a staging repository at the end of the buildand can be executed in the same build as the publishing task. This allows
having automatic releases without permanently enabling them.
publishToMavenCentral
as alias for runningpublishAllPublicationsToMavenCentralRepository
.publishAndReleaseToMavenCentral
as alias for running both of the above.coordinates(...)
and leave the others at their default value.Thanks to @sschuberth for the contribution.
java-test-fixture
projects being broken with Gradle 8.6.closeAndReleaseRepository
in favor ofreleaseRepository
.Minimum supported versions
Compatibility tested up to
Configuration cache status
When using Gradle 8.1 or newer configuration cache is generally supported.
Exceptions to that are:
v0.26.0
Compare Source
configure(Platform)
from the main plugin to modifywhat is getting published. Check out the docs for more details
configureBasedOnAppliedPlugins
DSL method toallow applying the default
configure
logic of the main plugin.configure(Platform)
now validates that the required plugins areapplied (e.g. Android Gradle Plugin for Android projects).
times for Gradle plugin projects with more than one publication. Thanks to
@autonomousapps for the fix.
next release, because the Kotlin/JS plugin has been deprecated.
from
simpleJavadocJar
toplainJavadocJar
. Thanks to @sschuberth.Minimum supported versions
Compatibility tested up to
Configuration cache status
When using Gradle 8.1 or newer configuration cache is generally supported.
Exceptions to that are:
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.
This PR was generated by Mend Renovate. View the repository job log.