Bump gradle-maven-publish-plugin from 0.14.2 to 0.23.1

[dependabot[bot]]

Bumps gradle-maven-publish-plugin from 0.14.2 to 0.23.1.

Release notes

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

0.23.1

Changelog

0.23.0

Changelog

0.22.0

CHANGELOG

0.21.0

Changelog

0.20.0

Changelog

0.19.0

Changelog

0.18.0

Changelog

0.17.0

Changelog

0.16.0

Changelog

0.15.1

Changelog

0.15.0

Changelog

Changelog

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

Version 0.23.1 (2022-12-30)

• 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

Version 0.23.0 (2022-12-29)

Updated docs can be found on the new website.

• NEW: It is now possible to set group id, artifact id directly through the DSL

  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.

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)
</tr></table> 

... (truncated)

Commits

• 55b2fbf Prepare for release 0.23.1.
• 925f5d2 also setup test fixtures sources jar for Kotlin/JVM, suppress warnings (#486)
• a05892d update branch name in actions
• 08f2406 test against Gradle 8.0-rc-1 (#485)
• 6f60a18 remove unused test dependencies (#484)
• aae16f7 Update dependency com.vanniktech:gradle-maven-publish-plugin to v0.23.0 (#483)
• 8d84276 Prepare for next development version
• 1f8a8c1 Prepare for release 0.23.0.
• c6d8640 typo2
• bc3a43e typo
• Additional commits viewable in compare view

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)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.