Update dependency com.vanniktech:gradle-maven-publish-plugin to v0.34.0 #24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/com.vanniktech-gradle-maven-publish-plugin-0.x
branch
from
65d2efd to
70aedda
Compare
renovate
bot
force-pushed
the
renovate/com.vanniktech-gradle-maven-publish-plugin-0.x
branch
from
70aedda to
9270c46
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/com.vanniktech-gradle-maven-publish-plugin-0.x
branch
from
9270c46 to
786cffa
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/com.vanniktech-gradle-maven-publish-plugin-0.x
branch
from
786cffa to
31f3fae
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/com.vanniktech-gradle-maven-publish-plugin-0.x
branch
from
31f3fae to
e2eece0
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.18.0->0.34.0Release Notes
vanniktech/gradle-maven-publish-plugin (com.vanniktech:gradle-maven-publish-plugin)
v0.34.0Compare Source
0.33.0 release notes for upgrade
instructions if you haven't upgraded yet.
SonatypeHosthas been removed from the DSL.SONATYPE_HOSTonly supportsCENTRAL_PORTALnow. It's recommended to use the following properties instead:mavenCentralPublishing=truereplacesSONATYPE_HOST=CENTRAL_PORTAL.mavenCentralAutomaticPublishing=truereplacesSONATYPE_AUTOMATIC_RELEASE=true.publishtasks.Thanks to @Goooler and @solrudev for their contributions to this release.
Minimum supported versions
Compatibility tested up to
v0.33.0Compare Source
BREAKING
publishToMavenCentral()andpublishToMavenCentral(automaticRelease)withoutSonatypeHostwillnow publish through the Central Portal.
publishToMavenCentralthat take aSonatypeHostparameter.SonatypeHost.New
com.android.fused-library. There are currently several limitationson the Android Gradle plugin side which make signing as well as publishing sources/javadocs not possible.
Improvements
mavenCentralPublishing=truereplacesSONATYPE_HOST=CENTRAL_PORTAL.mavenCentralAutomaticPublishing=truereplacesSONATYPE_AUTOMATIC_RELEASE=true.signAllPublications=truereplacesRELEASE_SIGNING_ENABLED=true.pomFromGradleProperties()is not called.TaskProvidertoJavadocJar.Dokka.-javadocjars (locally, the name of the published artifact is unchanged).versionto be read too early when publishing to Central Portal.Thanks to @Goooler, @solrudev and @sschuberth for their contributions to this release.
Minimum supported versions
Compatibility tested up to
v0.32.0Compare Source
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
V2Enabled.v0.31.0Compare Source
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
V2Enabled.v0.30.0Compare Source
org.jetbrains.dokka.experimental.gradle.pluginMode=V2Enabled.org.jetbrains.dokkaandorg.jetbrains.dokka-javadoc.org.jetbrains.dokka-androidplugin.httpsurl inSONATYPE_HOSTGradle property.Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
V2Enabled.v0.29.0Compare Source
configureBasedOnAppliedPlugins(sourcesJar: Boolean, javadocJar: Boolean)overload that allows disabling sources and javadoc jars without having to use the more granular
PlatformAPIs.afterEvaluateanymore, making manual overrides easier.Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
v0.28.0Compare Source
this use the
CENTRAL_PORTALoption when specifying the Sonatype host.releasevariant if the projecthas an Android target and no variant was explicitly specified through the Kotlin Gradle DSL.
KotlinMultiplatform(...).closeAndReleaseRepositorytask. UsereleaseRepository, whichis functionally equivalent, instead.
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
v0.27.0Compare Source
releaseRepositoryreleases a staging repository at the end of the build and can be executed in the same buildas the publishing task. This allows having automatic releases without permanently enabling them.
publishToMavenCentralas alias for runningpublishAllPublicationsToMavenCentralRepository.publishAndReleaseToMavenCentralas alias for running both of the above.coordinates(...)and leave the others at their default value.Thanks to @sschuberth for the contribution.
java-test-fixtureprojects being broken with Gradle 8.6.closeAndReleaseRepositoryin 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.0Compare Source
configure(Platform)from the main plugin to modifywhat is getting published. Check out the docs for more details
configureBasedOnAppliedPluginsDSL method toallow applying the default
configurelogic 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
simpleJavadocJartoplainJavadocJar. 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:
v0.25.3Compare Source
java-test-fixturesplugin.v0.25.2Compare Source
v0.25.1Compare Source
v0.25.0Compare Source
createStagingRepositorytask now uses the worker API which allows the project to built-inparallel to the creation of the staging repository.
care of creating the sources jar on its own. Because of this the base plugin won't allow disabling
sources jar creation for Kotlin/JS projects anymore starting with 1.8.20. The
KotlinJsconstructorwith a
sourcesJarparameter has been deprecated.java-test-fixturesprojects.com.gradle.plugin-publish1.0.0 and 1.1.0.com.gradle.plugin-publish1.0.0commonsources jar for multiplatform projects will only containthe sources of the common source set instead of containing the sources from all source sets.
Configuration cache status
Configuration cache is supported starting with Gradle 7.6+ except for:
v0.24.0Compare Source
v0.23.2Compare Source
The plugin will also fallback to any staging profile that has a matching prefix with the group id.
java-test-fixturesprojects,project.groupandproject.versionare now being set again for those projects. #490v0.23.1Compare Source
java-test-fixturesplugin in Kotlin/JVM projects.java-test-fixtures.v0.23.0Compare Source
Updated docs can be found on the new website.
mavenPublishing { coordinates("com.example", "library", "1.0.3") }project.groupandproject.versionwill still be used as default values for group and version if theGROUP/VERSION_NAMEGradle properties do not exist andcoordinateswas not called, however there are 2behavior changes:
GROUPandVERSION_NAMEGradle properties take precedence overproject.groupandproject.versioninsteadof being overwritten by them. If you need to define the properties but replace them for some projects,
please use the new
coordinatesmethod instead.GROUPandVERSION_NAMEGradle properties will not be explicitly set asproject.groupandproject.versionanymore.dropRepositorytask that will drop a Sonatype staging repository. It is possible to specifywhich repository to drop by adding a
--repositoryparameter with the id of the staging repository that wasprinted during
publish. If no repository is specified and there is only one staging repository, that onewill be dropped.
java-test-fixturesplugin.v0.22.0Compare Source
SONATYPE_HOSTor callingpublishToMavenCentral(...)the plugin will now explicitly create a staging repository on Sonatype. This avoids issues where a single build would
create multiple repositories.
--no-paralleland--no-daemontogether withpublishpublishorpublishAllPublicationsToMavenCentralRepositorytasksthe plugin will automatically close the staging repository at the end of the build if it was successful.
or
closeAndReleaseRepositorytask is not needed anymore.com.gradle.plugin-publishplugin.v0.21.0Compare Source
Minimum supported Gradle version is now 7.2.0
Minimum supported Android Gradle Plugin versions are now 7.1.2, 7.2.0-beta02 and 7.3.0-alpha01
Behavior changes
The
com.vanniktech.maven.publishstops adding Maven Central (Sonatype OSS) as apublishing target and will not enable GPG signing by default. To continue publishing to maven central and signing artifacts either add the following to your
gradle.properties:SONATYPE_HOST=DEFAULTv0.20.0Compare Source
Upcoming behavior change
In the next release after this the
com.vanniktech.maven.publishwill stop adding Maven Central (Sonatype OSS) as apublishing target and will not enable GPG signing by default. If you are currently relying on this behavior the plugin
will print a warning during configuration phase. To continue publishing to maven central and signing artifacts either
add this to your build files:
or the following to your
gradle.properties:v0.19.0Compare Source
of a library unless
androidVariantToPublishwas set in the DSL. This means that for example bothdebugandreleaseor all flavors.
androidVariantToPublish. In the future the main plugin will always publish all variants of an Androidlibrary. If you need to publish only one variant or a subset take a look at the base plugin
APIs.
AndroidSingleVariantLibraryandAndroidMultiVariantLibraryoptions that use the new AGP 7.1APIs under the hood.
AndroidLibraryoption in favor of the abovecom.vanniktech:nexus:<version>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.