search

ankidroid / Anki-Android-Backend

JNI bridge between AnkiDroid and Anki Desktop's rust code
GNU General Public License v3.0
68 stars 26 forks source link

build(deps): bump com.vanniktech:gradle-maven-publish-plugin from 0.26.0 to 0.28.0 #360

Closed dependabot[bot] closed 7 months ago

dependabot[bot] commented 7 months ago

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

Release notes

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

0.28.0

  • Added support for publishing through the new Central Portal. To use this use the CENTRAL_PORTAL option when specifying the Sonatype host.
  • For Kotlin Multiplatform the main plugin will now automatically publish the release variant if the project has an Android target and no variant was explicitly specified through the Kotlin Gradle DSL.
  • Support specifying the Android variants to publish in KotlinMultiplatform(...).
  • Updated minimum supported Gradle, Android Gradle Plugin and Kotlin versions.
  • Removed support for the deprecated Kotlin/JS plugin.
  • Removed the deprecated closeAndReleaseRepository task. Use releaseRepository, which is functionally equivalent, instead.

Minimum supported versions

  • JDK 11
  • Gradle 8.1
  • Android Gradle Plugin 8.0.0
  • Kotlin Gradle Plugin 1.9.20

Compatibility tested up to

  • JDK 21
  • Gradle 8.6
  • Gradle 8.7-rc-3
  • Android Gradle Plugin 8.3.0
  • Android Gradle Plugin 8.4.0-alpha13
  • Kotlin Gradle Plugin 1.9.23
  • Kotlin Gradle Plugin 2.0.0-Beta4

Configuration cache status

Configuration cache is generally supported, except for:

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

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

... (truncated)

Changelog

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

0.28.0 (2024-03-12)

  • Added support for publishing through the new Central Portal. To use this use the CENTRAL_PORTAL option when specifying the Sonatype host.
  • For Kotlin Multiplatform the main plugin will now automatically publish the release variant if the project has an Android target and no variant was explicitly specified through the Kotlin Gradle DSL.
  • Support specifying the Android variants to publish in KotlinMultiplatform(...).
  • Updated minimum supported Gradle, Android Gradle Plugin and Kotlin versions.
  • Removed support for the deprecated Kotlin/JS plugin.
  • Removed the deprecated closeAndReleaseRepository task. Use releaseRepository, which is functionally equivalent, instead.

Minimum supported versions

  • JDK 11
  • Gradle 8.1
  • Android Gradle Plugin 8.0.0
  • Kotlin Gradle Plugin 1.9.20

Compatibility tested up to

  • JDK 21
  • Gradle 8.6
  • Gradle 8.7-rc-3
  • Android Gradle Plugin 8.3.0
  • Android Gradle Plugin 8.4.0-alpha13
  • Kotlin Gradle Plugin 1.9.23
  • Kotlin Gradle Plugin 2.0.0-Beta4

Configuration cache status

Configuration cache is generally supported, except for:

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

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.

... (truncated)

Commits
  • 2f72723 update changelog for 0.28.0
  • dd412fc test Gradle 8.7-rc3 (#737)
  • c5019ea add release Android target by default for KMP (#736)
  • 2ccf77c support publishing through central portal (#733)
  • e80a256 remove closeAndReleaseRepository task (#734)
  • 3d66614 update tested versions (#735)
  • e92141b chore(deps): update gradle/gradle-build-action action to v3 (#732)
  • b267449 fix(deps): update truth to v1.4.2 (#723)
  • d241fd3 fix(deps): update dependency org.jetbrains.dokka:dokka-gradle-plugin to v1.9....
  • 02a60a5 chore(deps): update softprops/action-gh-release action to v2 (#731)
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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)
dependabot[bot] commented 7 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.