chore(deps): update plugin mavenpublish to v0.37.0 - #1312
Conversation
da3b4c3 to
6a61834
Compare
6a61834 to
cf6b45a
Compare
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit cf6b45a. Configure here.
| dokka = { id = "org.jetbrains.dokka", version = "1.9.20" } | ||
| spotless = { id = "com.diffplug.spotless", version = "8.7.0" } | ||
| mavenPublish = { id = "com.vanniktech.maven.publish", version = "0.27.0" } | ||
| mavenPublish = { id = "com.vanniktech.maven.publish", version = "0.37.0" } |
There was a problem hiding this comment.
Maven publish needs Gradle 9
High Severity
Bumping com.vanniktech.maven.publish to 0.37.0 while the wrapper stays on Gradle 8.14.5 conflicts with that release’s minimum Gradle 9.0.0 (from 0.36.0). The catalog is used by plugin-build and sentry-kotlin-compiler-plugin, so preMerge, :check, and snapshot publish are likely to fail at configuration.
Reviewed by Cursor Bugbot for commit cf6b45a. Configure here.
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |


This PR contains the following updates:
0.27.0→0.37.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
vanniktech/gradle-maven-publish-plugin (com.vanniktech.maven.publish)
v0.37.0Compare Source
.ascsignature files (gradle/gradle#20232) and the
sha256/sha512checksums, which are never read by Gradle or Maven Central. The published checksums can be configured through
checksums(...)in the DSL or themavenCentralChecksumsGradle property (defaultmd5,sha1). Signature checksumexclusion can be controlled through
excludeSignatureChecksums()or themavenCentralExcludeSignatureChecksumsGradle property.
Minimum supported versions
Compatibility tested up to
v0.36.0Compare Source
BREAKING
DirectorySignatureTypeinternal.Behavior changes
validateDeploymentnow has theDeploymentValidationenum as type instead of being a boolean. The defaultis now to just wait for the
VALIDATEDstate. The previous behavior can be achieved by setting it toPUBLISHED.NONEcan be used for disabling the validation completely.configure(...)manually to configure what to publish and not passingjavadocJarexplicity,the plugin now defaults to publishing an empty javadoc jar.
Features
when using the default options and the Dokka plugin is applied to the project.
JavadocJarandSourcesJaroptions toconfigureBasedOnAppliedPluginsand to allapplicable project types that can be passed to
configure. The previousBooleanbased versions havebeen deprecated.
mavenCentralDeploymentValidationandmavenCentralAutomaticPublishingare used for the default values of the 2 parameters when they are not passedexplicitly. This allows to more easily override them in certain environments.
gradle.propertiesfiles are now considered inthe same way they are when isolated projects is disabled.
Improvements
Minimum supported versions
Compatibility tested up to
v0.35.0Compare Source
com.android.kotlin.multiplatform.library.SONATYPE_HOSTis not set toCENTRAL_PORTAL.Thanks to @joshfriend, @Flowdalic and @Goooler for their contributions to this release.
Minimum supported versions
Compatibility tested up to
v0.34.0Compare Source
0.33.0 release notes for upgrade
instructions if you haven't upgraded yet.
SonatypeHosthas been removed from the DSL.SONATYPE_HOSTonly supportsCENTRAL_PORTALnow. It's recommended to use the following properties instead:mavenCentralPublishing=truereplacesSONATYPE_HOST=CENTRAL_PORTAL.mavenCentralAutomaticPublishing=truereplacesSONATYPE_AUTOMATIC_RELEASE=true.publishtasks.Thanks to @Goooler and @solrudev for their contributions to this release.
Minimum supported versions
Compatibility tested up to
v0.33.0Compare Source
BREAKING
publishToMavenCentral()andpublishToMavenCentral(automaticRelease)withoutSonatypeHostwillnow publish through the Central Portal.
publishToMavenCentralthat take aSonatypeHostparameter.SonatypeHost.New
com.android.fused-library. There are currently several limitationson the Android Gradle plugin side which make signing as well as publishing sources/javadocs not possible.
Improvements
mavenCentralPublishing=truereplacesSONATYPE_HOST=CENTRAL_PORTAL.mavenCentralAutomaticPublishing=truereplacesSONATYPE_AUTOMATIC_RELEASE=true.signAllPublications=truereplacesRELEASE_SIGNING_ENABLED=true.pomFromGradleProperties()is not called.TaskProvidertoJavadocJar.Dokka.-javadocjars (locally, the name of the published artifact is unchanged).versionto be read too early when publishing to Central Portal.Thanks to @Goooler, @solrudev and @sschuberth for their contributions to this release.
Minimum supported versions
Compatibility tested up to
v0.32.0Compare Source
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
V2Enabled.v0.31.0Compare Source
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
V2Enabled.v0.30.0Compare Source
org.jetbrains.dokka.experimental.gradle.pluginMode=V2Enabled.org.jetbrains.dokkaandorg.jetbrains.dokka-javadoc.org.jetbrains.dokka-androidplugin.httpsurl inSONATYPE_HOSTGradle property.Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
V2Enabled.v0.29.0Compare Source
configureBasedOnAppliedPlugins(sourcesJar: Boolean, javadocJar: Boolean)overload that allows disabling sources and javadoc jars without having to use the more granular
PlatformAPIs.afterEvaluateanymore, making manual overrides easier.Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
v0.28.0Compare Source
this use the
CENTRAL_PORTALoption when specifying the Sonatype host.releasevariant if the projecthas an Android target and no variant was explicitly specified through the Kotlin Gradle DSL.
KotlinMultiplatform(...).closeAndReleaseRepositorytask. UsereleaseRepository, whichis functionally equivalent, instead.
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.