Bump com.vanniktech:gradle-maven-publish-plugin from 0.26.0 to 0.27.0

[dependabot]

Bumps com.vanniktech:gradle-maven-publish-plugin from 0.26.0 to 0.27.0.

Release notes

Sourced from com.vanniktech:gradle-maven-publish-plugin's releases.

0.27.0

• Added new publishing related tasks
  • releaseRepository releases a staging repository at the end of the build and can be executed in the same build as the publishing task. This allows having automatic releases without permanently enabling them.
  • publishToMavenCentral as alias for running publishAllPublicationsToMavenCentralRepository.
  • publishAndReleaseToMavenCentral as alias for running both of the above.
  • For more information checkout the docs.
• It is now possible to only pass a subset of the parameters to coordinates(...) and leave the others at their default value. Thanks to @​sschuberth for the contribution.
• Fixed java-test-fixture projects being broken with Gradle 8.6.
• Deprecated closeAndReleaseRepository in favor of releaseRepository.

Minimum supported versions

• JDK 11
• Gradle 7.6
• Android Gradle Plugin 7.4.0
• Kotlin Gradle Plugin 1.8.20

Compatibility tested up to

• JDK 21
• Gradle 8.5
• Gradle 8.6-rc-1
• Android Gradle Plugin 8.2.1
• Android Gradle Plugin 8.3.0-beta01
• Android Gradle Plugin 8.4.0-alpha03
• Kotlin Gradle Plugin 1.9.22
• Kotlin Gradle Plugin 2.0.0-Beta2

Configuration cache status

When using Gradle 8.1 or newer configuration cache is generally supported.

Exceptions to that are:

• Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](gradle/gradle#22779).
• Dokka does not support configuration cache

Changelog

Sourced from com.vanniktech:gradle-maven-publish-plugin's changelog.

0.27.0 (2024-01-06)

• Added new publishing related tasks
  • releaseRepository releases a staging repository at the end of the build and can be executed in the same build as the publishing task. This allows having automatic releases without permanently enabling them.
  • publishToMavenCentral as alias for running publishAllPublicationsToMavenCentralRepository.
  • publishAndReleaseToMavenCentral as alias for running both of the above.
  • For more information checkout the docs.
• It is now possible to only pass a subset of the parameters to coordinates(...) and leave the others at their default value. Thanks to @​sschuberth for the contribution.
• Fixed java-test-fixture projects being broken with Gradle 8.6.
• Deprecated closeAndReleaseRepository in favor of releaseRepository.

Minimum supported versions

• JDK 11
• Gradle 7.6
• Android Gradle Plugin 7.4.0
• Kotlin Gradle Plugin 1.8.20

Compatibility tested up to

• JDK 21
• Gradle 8.5
• Gradle 8.6-rc-1
• Android Gradle Plugin 8.2.1
• Android Gradle Plugin 8.3.0-beta01
• Android Gradle Plugin 8.4.0-alpha03
• Kotlin Gradle Plugin 1.9.22
• Kotlin Gradle Plugin 2.0.0-Beta2

Configuration cache status

When using Gradle 8.1 or newer configuration cache is generally supported.

Exceptions to that are:

• Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](gradle/gradle#22779).
• Dokka does not support configuration cache

Commits

• 0139cc8 use 0.27.0-rc2
• 78d4a65 use 0.27.0-rc2
• 55c7960 fix stagingRepositoryId check (#703)
• 21de520 use new tasks
• 2c51b87 Update to 0.27.0-rc1
• 66b8efe Changelog for 0.27.0 (#702)
• 7936143 add new release task (#699)
• 4fb8a9f fix(deps): update dependency com.android.tools.build:gradle to v8.2.1 (#701)
• eed76ce chore(deps): update plugin buildconfig to v5.3.2 (#700)
• 8558785 always close, release and drop from build service (#698)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)