search

dokar3 / ChipTextField

Editable chip layout for Compose Multiplatform
Apache License 2.0
91 stars 4 forks source link

Bump gradle-maven-publish-plugin from 0.21.0 to 0.22.0 #38

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps gradle-maven-publish-plugin from 0.21.0 to 0.22.0.

Changelog

Sourced from gradle-maven-publish-plugin's changelog.

Version 0.22.0 (2022-09-09)

  • 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
Commits
  • 7df14f3 Prepare for release 0.22.0
  • 3dd754a Use version catalog to manage dependencies to make renovate work again (#412)
  • 0dc4587 prepare changelog for next release (#411)
  • 0db5be2 drop repository when build fails (#410)
  • 19a8631 retrieve activity messages when closing repository fails (#409)
  • d28e119 Use composite builds instead of buildSrc (#408)
  • 5e48420 Create nexus lazily to avoid an error when properties aren't set (#405)
  • 86b2c8f workaround issues with the signing setup (#404)
  • c143338 automatically close the created repository and optionally also release it (#403)
  • 482502d detect when closing the repository failed (#402)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)