renovate[bot]
commented
1 year ago 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.
This PR contains the following updates:
0.14.2->0.25.2Release Notes
vanniktech/gradle-maven-publish-plugin
### [`v0.25.2`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0252--2023-04-16-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.25.1...0.25.2) - Fix javadoc jar being empty when using dokka. ### [`v0.25.1`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0251--2023-03-24-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.25.0...0.25.1) - Fix snapshot publishing being broken. ### [`v0.25.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0250--2023-03-23-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.24.0...0.25.0) - The `createStagingRepository` task now uses the worker API which allows the project to built in parallel to the creation of the staging repository. - Fix incompatibility with Kotlin 1.8.20-Beta for Kotlin/JS projects. The Kotlin/JS plugin is now taking 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 `KotlinJs` constructor with a `sourcesJar` parameter has been deprecated. - Fix incompatibility with Gradle 8.1 for `java-test-fixtures` projects - Fix incompatibility with `com.gradle.plugin-publish` 1.0.0 and 1.1.0 - New minimum supported versions: - Gradle 7.4 - Android Gradle Plugin 7.3.0 - Kotlin Gradle Plugin 1.7.0 - `com.gradle.plugin-publish` 1.0.0 - Note: Starting with Kotlin 1.8.20-Beta the `common` sources jar for multiplatform projects will only contain the 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: - Builds with enabled signing, will be resolved in Gradle 8.1. - Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](https://togithub.com/gradle/gradle/issues/22779). - Kotlin Multiplatform projects, blocked by [KT-49933](https://youtrack.jetbrains.com/issue/KT-49933). ### [`v0.24.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0240--2023-01-29-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.23.2...0.24.0) - Support arbitrary Sonatype hosts instead of just oss.sonatype.org and s01.oss.sonatype.org. - Support adjusting timeouts for Sonatype related requests and operations. [See docs](https://vanniktech.github.io/gradle-maven-publish-plugin/central/#timeouts) - Internal change on how the sources jar is created. ### [`v0.23.2`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0232--2023-01-17-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.23.1...0.23.2) - Fix signing when using Gradle 8.0. - Finding a matching staging profile in Sonatype is more lenient. If there is just one that one will always be used. The plugin will also fallback to any staging profile that has a matching prefix with the group id. - As a workaround for an issue in Gradle that causes invalid module metadata for `java-test-fixtures` projects, `project.group` and `project.version` are now being set again for those projects. [#490](https://togithub.com/vanniktech/gradle-maven-publish-plugin/pull/490) ### [`v0.23.1`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0231--2022-12-30-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.23.0...0.23.1) - Also support publishing sources for the `java-test-fixtures` plugin in Kotlin/JVM projects. - Suppress Gradle warnings when publishing a project that uses `java-test-fixtures`. ### [`v0.23.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0230--2022-12-29-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.22.0...0.23.0) Updated docs can be found on [the new website](https://vanniktech.github.io/gradle-maven-publish-plugin/). - **NEW**: It is now possible to set group id, artifact id directly through the DSL ```groovy mavenPublishing { coordinates("com.example", "library", "1.0.3") } ``` - `project.group` and `project.version` will still be used as default values for group and version if the `GROUP`/`VERSION_NAME` Gradle properties do not exist and `coordinates` was not called, however there are 2 **behavior changes**: - The `GROUP` and `VERSION_NAME` Gradle properties take precedence over `project.group` and `project.version` instead of being overwritten by them. If you need to define the properties but replace them for some projects, please use the new `coordinates` method instead. - The `GROUP` and `VERSION_NAME` Gradle properties will not be explicitly set as `project.group` and `project.version` anymore. - **NEW**: Added `dropRepository` task that will drop a Sonatype staging repository. It is possible to specify which repository to drop by adding a `--repository` parameter with the id of the staging repository that was printed during `publish`. If no repository is specified and there is only one staging repository, that one will be dropped. - Added workaround to also publish sources for the `java-test-fixtures` plugin - Fixed publishing Kotlin/JS projects with the base plugin. - Fixed that a POM configured through the DSL is incomplete when publishing Gradle plugins. - The minimum supported Gradle version has been increased to 7.3. - The plugin now requires using JDK 11+ to run Gradle. ### [`v0.22.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0220--2022-09-09-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.21.0...0.22.0) - **NEW**: When publishing to maven central by setting `SONATYPE_HOST` or calling `publishToMavenCentral(...)` the plugin will now explicitly create a staging repository on Sonatype. This avoids issues where a single build would create multiple repositories - The above change means that the plugin supports parallel builds and it is not neccessary anymore to use `--no-parallel` and `--no-daemon` together with `publish` - **NEW**: When publishing with the `publish` or `publishAllPublicationsToMavenCentralRepository` tasks the plugin will automatically close the staging repository at the end of the build if it was successful. - **NEW**: Option to also automatically release the staging repository after closing was susccessful SONATYPE_HOST=DEFAULT # or S01 SONATYPE_AUTOMATIC_RELEASE=true or mavenPublishing { publishToMavenCentral("DEFAULT", true) // or publishToMavenCentral("S01", true) } - in case the option above is enabled, the `closeAndReleaseRepository` task is not needed anymore - when closing the repository fails the plugin will fail the build immediately instead of timing out - when closing the repository fails the plugin will try to print the error messages from Nexus - increased timeouts for calls to the Sonatype Nexus APIs - fixed incompatibility with the `com.gradle.plugin-publish` plugin - added wokaround for Kotlin multiplatform builds reporting disabled build optimizations (see [KT-46466](https://youtrack.jetbrains.com/issue/KT-46466)) ### [`v0.21.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0210--2022-07-11-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.20.0...0.21.0) 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.publish` stops adding Maven Central (Sonatype OSS) as a publishing 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`: ```properties SONATYPE_HOST=DEFAULT ``` ### [`v0.20.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0200--2022-06-02-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.19.0...0.20.0) **Upcoming behavior change** In the next release after this the `com.vanniktech.maven.publish` will stop adding Maven Central (Sonatype OSS) as a publishing 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: ```gradle mavenPublishing { publishToMavenCentral() // use publishToMavenCentral("S01") for publishing through s01.oss.sonatype.org signAllPublications() } ``` or the following to your `gradle.properties`: ```gradle SONATYPE_HOST=DEFAULT ``` ### [`v0.19.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0190--2022-02-26-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.18.0...0.19.0) - **Behavior Change:** When using version 7.1.0 or newer of the Android Gradle Plugin we will now publish all variants of a library unless `androidVariantToPublish` was set in the DSL. This means that for example both `debug` and `release` or all flavors. - Deprecated `androidVariantToPublish`. In the future the main plugin will always publish all variants of an Android library. If you need to publish only one variant or a subset take a look at the [base plugin](README.md#base-plugin) APIs. - Base plugin: Added `AndroidSingleVariantLibrary` and `AndroidMultiVariantLibrary` options that use the new AGP 7.1 APIs under the hood. - Base plugin: Deprecated `AndroidLibrary` option in favor of the above - The integration with Sonatype Nexus has been extracted into it's own artifact and is available as `com.vanniktech:nexus: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 has been generated by Mend Renovate. View repository job log here.