vanniktech/gradle-maven-publish-plugin
### [`v0.22.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#Version-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
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, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
0.21.0->0.22.0Release Notes
vanniktech/gradle-maven-publish-plugin
### [`v0.22.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#Version-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 optimizationsConfiguration
📅 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.