customizable-okhttp-logging-interceptor
customizable-okhttp-logging-interceptor copied to clipboard
Bump com.vanniktech.maven.publish from 0.30.0 to 0.32.0
Bumps com.vanniktech.maven.publish from 0.30.0 to 0.32.0.
Release notes
Sourced from com.vanniktech.maven.publish's releases.
0.32.0
- Improve names of Central Portal deployments.
- Fix an issue where the wrong staging profile for (s01.)oss.sonatype.org was selected when publishing to Maven Central.
- Fix incompatibility with Kotlin 1.9.x when used through compiled plugins.
- Improve error message when not being able to detect Kotlin plugin.
- Fix an issue with detecting whether configuration cache is enabled which lead to a not actionable error message.
- Fix compatibility with Gradle 9.0.
Minimum supported versions
- JDK 11
- Gradle 8.5
- Android Gradle Plugin 8.0.0
- Kotlin Gradle Plugin 1.9.20
Compatibility tested up to
- JDK 24
- Gradle 8.14
- Gradle 9.0-milestone-6
- Android Gradle Plugin 8.10.0
- Android Gradle Plugin 8.11.0-alpha10
- Kotlin Gradle Plugin 2.1.20
- Kotlin Gradle Plugin 2.1.21-RC2
- Kotlin Gradle Plugin 2.2.0-Beta2
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).
- When using Dokka 1.x or Dokka 2.x without
0.31.0
- Add support for publishing snapshots to Central Portal.
- Make sure to enable snapshots for your namespace on central.sonatype.com.
- Thanks to
@solrudevfor the contribution.- Add support for multiple matching staging profiles by taking the one with the longest matching prefix.
Minimum supported versions
- JDK 11
- Gradle 8.5
- Android Gradle Plugin 8.0.0
- Kotlin Gradle Plugin 1.9.20
Compatibility tested up to
- JDK 23
- Gradle 8.13
... (truncated)
Changelog
Sourced from com.vanniktech.maven.publish's changelog.
0.32.0 UNRELEASED
- Improve names of Central Portal deployments.
- Fix an issue where the wrong staging profile for (s01.)oss.sonatype.org was selected when publishing to Maven Central.
- Fix incompatibility with Kotlin 1.9.x when used through compiled plugins.
- Improve error message when not being able to detect Kotlin plugin.
- Fix an issue with detecting whether configuration cache is enabled which lead to a not actionable error message.
- Fix compatibility with Gradle 9.0.
Minimum supported versions
- JDK 11
- Gradle 8.5
- Android Gradle Plugin 8.0.0
- Kotlin Gradle Plugin 1.9.20
Compatibility tested up to
- JDK 24
- Gradle 8.14
- Gradle 9.0-milestone-6
- Android Gradle Plugin 8.10.0
- Android Gradle Plugin 8.11.0-alpha10
- Kotlin Gradle Plugin 2.1.20
- Kotlin Gradle Plugin 2.1.21-RC2
- Kotlin Gradle Plugin 2.2.0-Beta2
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).
- When using Dokka 1.x or Dokka 2.x without
V2Enabled0.31.0 (2025-03-06)
- Add support for publishing snapshots to Central Portal.
- Make sure to enable snapshots for your namespace on central.sonatype.com.
- Thanks to
@solrudevfor the contribution.- Add support for multiple matching staging profiles by taking the one with the longest matching prefix.
Minimum supported versions
- JDK 11
- Gradle 8.5
- Android Gradle Plugin 8.0.0
- Kotlin Gradle Plugin 1.9.20
Compatibility tested up to
- JDK 23
... (truncated)
Commits
b016437Update libs.versions.toml348cf2ffix(deps): update kotlin monorepo to v2.1.21 (#969)9433064Changelog for 0.32.0cb7699cchore(deps): update dependency gradle to v9.0-milestone-6 (#951)e103b07chore(deps): update android.gradle (#962)0f8196cchore(deps): update plugin buildconfig to v5.6.5 (#961)442c178fix(deps): update dependency com.android.tools.build:gradle to v8.10.0 (#963)705be5bchore(deps): update plugin buildconfig to v5.6.4 (#960)df41872Mark JavadocJar as a sealed interface (#959)8dab2beTweak version catalog usages (#957)- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)