Bump gradle-maven-publish-plugin from 0.19.0 to 0.20.0

[dependabot[bot]]

Bumps gradle-maven-publish-plugin from 0.19.0 to 0.20.0.

Release notes

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

0.20.0

Changelog

Changelog

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

Version 0.20.0 (2022-06-02)

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 curretly 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:

mavenPublishing {
  publishToMavenCentral() // use publishToMavenCentral("S01") for publishing through s01.oss.sonatype.org
  enableReleaseSigning()
}

or the following to your gradle.properties:

SONATYPE_HOST=DEFAULT
# SONATYPE_HOST=S01 for publishing through s01.oss.sonatype.org
RELEASE_SIGNING_ENABLED=true

The base plugin is unaffected by these changes because it already has this behavior.

Deprecation

The old mavenPublish extension has been deprecated.

If you were using it to set sonatypeHost to S01 use

mavenPublishing {
  publishToMavenCentral("S01")
}

instead or add SONATYPE_HOST=S01 to your gradle.properties.

If sonatypeHost was used to disable adding Maven Central as a publishing target add SONATYPE_HOST= until 0.21.0 is out and this becomes the default behavior.

If you set releaseSigningEnabled to false add RELEASE_SIGNING_ENABLED=false to your gradle.properties until 0.21.0 is out and this becomes the default behavior.

New

Added support to set the following pom values through properties (thanks to @​jaredsburrows for the contribution)

• POM_ISSUE_SYSTEM sets issueManagement.system
• POM_ISSUE_URL sets issueManagement.url
• POM_DEVELOPER_EMAIL sets developer.email

Fixed

... (truncated)

Commits

• 3005950 Prepare for release 0.20.0.
• 643bea0 update changelog for 0.20.0 (#352)
• 582f0d4 fix Kotlin MPP project not being configured when Android plugin is present (#...
• 399b0f9 fix legacy Android setup in mpp projects (#350)
• c8dd40c deprecate old mavenPublish extension (#340)
• 8e1f12d fix error message when no repo is found (#337)
• 6134aa0 Bump actions/setup-java from 2 to 3 (#348)
• e6fee7c Bump actions/checkout from 2 to 3 (#349)
• 9512622 Create dependabot.yml (#347)
• d03e6e5 Support more POM properties (#345)
• 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)