Bump gradle-maven-publish-plugin from 0.22.0 to 0.24.0

[dependabot]

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

Release notes

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

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
• Internal change on how the sources jar is created.

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

0.23.1

Changelog

0.23.0

Changelog

Changelog

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

0.24.0 (2023-01-29)

• 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
• Internal change on how the sources jar is created.

0.23.2 (2023-01-17)

• 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

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.

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.
• The plugin now requires using JDK 11+ to run Gradle.

Commits

• 7faa441 Prepare changelog for release 0.24.0.
• 95f5b4e make timeouts configurable (#508)
• 4b43020 replace custom sources jar task (#507)
• 744db56 Update dependency org.jlleitschuh.gradle:ktlint-gradle to v11.1.0 (#506)
• f041faa Open up SonatypeHost (#504)
• 9300a2b Update dependency com.vanniktech:gradle-maven-publish-plugin to v0.23.2 (#501)
• 8f3edf1 Update CHANGELOG for 0.23.2.
• b944e0d test against Gradle 8.0-rc-2 and AGP 8.0.0-alpha11 (#499)
• 93a2188 make finding a staging profile more lenient (#498)
• 6686704 Update dependency com.android.tools.build:gradle to v7.4.0 (#495)
• 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)