Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update plugin maven-publish to v0.28.0 #338

Merged
merged 3 commits into from
Mar 15, 2024

Conversation

juul-mobile-bot
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
com.vanniktech.maven.publish plugin minor 0.27.0 -> 0.28.0

Release Notes

vanniktech/gradle-maven-publish-plugin (com.vanniktech.maven.publish)

v0.28.0

Compare Source

  • 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.
  • Dokka does not support configuration cache

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Copy link

github-actions bot commented Mar 15, 2024

Test Results

 50 files  ±0   50 suites  ±0   22s ⏱️ +5s
252 tests ±0  252 ✅ ±0  0 💤 ±0  0 ❌ ±0 
297 runs  ±0  297 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 9fc09c9. ± Comparison against base commit 247c2dc.

♻️ This comment has been updated with latest results.

@twyatt twyatt enabled auto-merge (squash) March 15, 2024 09:32
@twyatt twyatt merged commit 171a693 into main Mar 15, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants