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

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

Release notes

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

0.21.0

Changelog

Changelog

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

Version 0.21.0 (2022-07-11)

Behavior changes

The com.vanniktech.maven.publish stops adding Maven Central (Sonatype OSS) as a publishing target and will not enable GPG signing by default. To continue publishing to maven central and signing artifacts either add the following to your gradle.properties:
SONATYPE_HOST=DEFAULT
# SONATYPE_HOST=S01 for publishing through s01.oss.sonatype.org
RELEASE_SIGNING_ENABLED=true
or add this to your Groovy build files:
mavenPublishing {
  publishToMavenCentral()
  // publishToMavenCentral("S01") for publishing through s01.oss.sonatype.org
  signAllPublications()
}
or the following to your kts build files:
mavenPublishing {
  publishToMavenCentral()
  // publishToMavenCentral(SonatypeHost.S01) for publishing through s01.oss.sonatype.org
  signAllPublications()
}
The base plugin is unaffected by these changes because it already has this behavior.

Android variant publishing

Since version 0.19.0 the plugin was publishing a multi variant library by default for Android projects. Due to a bug in Android Studio that will cause it to not find the sources for libraries published this way the plugin will temporarily revert to publishing single variant libraries again. Unless another variant is specified by setting the ANDROID_VARIANT_TO_PUBLISH Gradle property the release variant will be published.

To continue publishing multi variant libraries you can use the base plugin.

Removals

The deprecated mavenPublish extension has been removed. Take a look at the changelog for 0.20.0 for replacements.

Commits

41c1059 Prepare for release 0.21.0
3b9fe2d temporarily switch back to single variant publishing (#372)
0a564ae update kotlin to 1.7.10 (#373)
3939000 Update dependency com.android.tools.build:gradle to v7.2.1 (#361)
ab3b80d cleanup legacy code (#358)
de60b93 Nuke Gradle Versions Plugin (#370)
d59aba5 Update dependency org.jlleitschuh.gradle:ktlint-gradle to v10.3.0 (#368)
02c2fbc Update dependency gradle to v7.4.2 (#364)
097a2bf Configure Renovate (#359)
edc9ea6 remove legacy extension (#356)
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)

dokar3 / ChipTextField

Bump gradle-maven-publish-plugin from 0.20.0 to 0.21.0 #30

0.21.0

Version 0.21.0 (2022-07-11)