[Update]: Bump com.vanniktech.maven.publish from 0.25.3 to 0.26.0

[dependabot[bot]]

Bumps com.vanniktech.maven.publish from 0.25.3 to 0.26.0.

Release notes

Sourced from com.vanniktech.maven.publish's releases.

0.26.0

• It's now supported to call configure(Platform) from the main plugin to modify what is getting published. Check out the docs for more details
• The base plugin now has a configureBasedOnAppliedPlugins DSL method to allow applying the default configure logic of the main plugin.
• Calling configure(Platform) now validates that the required plugins are applied (e.g. Android Gradle Plugin for Android projects).
• It's now possible to disable source publishing for KMP projects.
• Fixed an issue which would cause the javadoc jar task to be registered multiple times for Gradle plugin projects with more than one publication. Thanks to @​autonomousapps for the fix.
• Publishing Kotlin/JS projects has been deprecated and will be removed in the next release, because the Kotlin/JS plugin has been deprecated.
• The internal task to create a javadoc jar for certain project types has been renamed from simpleJavadocJar to plainJavadocJar. Thanks to @​sschuberth.

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
• Android Gradle Plugin 8.2.0
• Android Gradle Plugin 8.3.0-alpha17
• Kotlin Gradle Plugin 1.9.21
• Kotlin Gradle Plugin 2.0.0-Beta1

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.maven.publish's changelog.

0.26.0 (2023-12-19)

• It's now supported to call configure(Platform) from the main plugin to modify what is getting published. Check out the docs for more details
• The base plugin now has a configureBasedOnAppliedPlugins DSL method to allow applying the default configure logic of the main plugin.
• Calling configure(Platform) now validates that the required plugins are applied (e.g. Android Gradle Plugin for Android projects).
• It's now possible to disable source publishing for KMP projects.
• Fixed an issue which would cause the javadoc jar task to be registered multiple times for Gradle plugin projects with more than one publication. Thanks to @​autonomousapps for the fix.
• Publishing Kotlin/JS projects has been deprecated and will be removed in the next release, because the Kotlin/JS plugin has been deprecated.
• The internal task to create a javadoc jar for certain project types has been renamed from simpleJavadocJar to plainJavadocJar. Thanks to @​sschuberth.

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
• Android Gradle Plugin 8.2.0
• Android Gradle Plugin 8.3.0-alpha17
• Kotlin Gradle Plugin 1.9.21
• Kotlin Gradle Plugin 2.0.0-Beta1

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

• 3da88b6 Update to 0.26.0-rc1
• e8fe14d update changelog
• 75abe99 fix classpath issue
• b308d56 fix(deps): update dependency org.jlleitschuh.gradle:ktlint-gradle to v12 (#668)
• 7d3972c chore(deps): update plugin buildconfig to v5 (#684)
• 4f57d1c chore(deps): update plugin com.gradle.enterprise to v3.16.1 (#683)
• 7bdff75 changelog for 0.26.0 (#681)
• 0b43d7f make it possible to use configure with the main plugin (#680)
• 6719275 updated tested versions (#679)
• 32e971a fix: resolve issue with attempting to register a task by the same name more t...
• 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)