-
Notifications
You must be signed in to change notification settings - Fork 12
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
fix(deps): update dependency com.vanniktech:gradle-maven-publish-plugin to v0.30.0 #280
fix(deps): update dependency com.vanniktech:gradle-maven-publish-plugin to v0.30.0 #280
Conversation
4f04943
to
1ec7bf3
Compare
4485dd9
to
9cc6113
Compare
9cc6113
to
c6124cd
Compare
8f87a9d
to
49da015
Compare
49da015
to
bbafb1a
Compare
6340e37
to
c74c7f1
Compare
c74c7f1
to
3d25718
Compare
3d25718
to
c2cc182
Compare
c2cc182
to
0ec1e81
Compare
0a3d799
to
dfe3681
Compare
dfe3681
to
09bb025
Compare
09bb025
to
c33a444
Compare
c33a444
to
9926252
Compare
9926252
to
9064ab1
Compare
This allows gradle-maven-publish-plugin to access KotlinMultiplatformExtension in build-support while avoiding a plugin version conflict in the main project. The desired version of the Kotlin compiler is still used.
9064ab1
to
d1b3087
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
@@ -11,7 +11,7 @@ repositories { | |||
} | |||
|
|||
dependencies { | |||
implementation(libs.kotlin.gradleApi) | |||
implementation(libs.kotlin.gradle) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated this because KotlinMultiplatformExtension
, needed by gradle-maven-publish-plugin, is not in the api
jar. Following KT-71604.
@@ -3,8 +3,8 @@ import org.jetbrains.kotlin.gradle.dsl.JvmTarget | |||
import org.jetbrains.kotlin.gradle.tasks.KotlinCompile | |||
|
|||
plugins { | |||
alias(libs.plugins.kotlin.jvm) apply false | |||
alias(libs.plugins.kotlin.multiplatform) apply false | |||
// Note: kotlin-jvm and kotlin-multiplatform plugins are added implicitly via build-support |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See discussion on vanniktech/gradle-maven-publish-plugin#883.
This PR contains the following updates:
0.25.3
->0.30.0
Release Notes
vanniktech/gradle-maven-publish-plugin (com.vanniktech:gradle-maven-publish-plugin)
v0.30.0
Compare Source
org.jetbrains.dokka.experimental.gradle.pluginMode=V2Enabled
org.jetbrains.dokka
andorg.jetbrains.dokka-javadoc
org.jetbrains.dokka-android
pluginhttps
url inSONATYPE_HOST
Gradle propertyMinimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
V2Enabled
v0.29.0
Compare Source
configureBasedOnAppliedPlugins(sourcesJar: Boolean, javadocJar: Boolean)
overload that allows disabling sources and javadoc jars without having to use
the more granular
Platform
APIs.includes the sources jar.
afterEvaluate
anymore, making manual overrides easier.optimizations.
to the error message.
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
v0.28.0
Compare Source
this use the
CENTRAL_PORTAL
option when specifying the Sonatype host.release
variant if the project has an Android target and no variant was explicitlyspecified through the Kotlin Gradle DSL.
KotlinMultiplatform(...)
.closeAndReleaseRepository
task. UsereleaseRepository
, whichis functionally equivalent, instead.
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
v0.27.0
Compare Source
releaseRepository
releases a staging repository at the end of the buildand can be executed in the same build as the publishing task. This allows
having automatic releases without permanently enabling them.
publishToMavenCentral
as alias for runningpublishAllPublicationsToMavenCentralRepository
.publishAndReleaseToMavenCentral
as alias for running both of the above.coordinates(...)
and leave the others at their default value.Thanks to @sschuberth for the contribution.
java-test-fixture
projects being broken with Gradle 8.6.closeAndReleaseRepository
in favor ofreleaseRepository
.Minimum supported versions
Compatibility tested up to
Configuration cache status
When using Gradle 8.1 or newer configuration cache is generally supported.
Exceptions to that are:
v0.26.0
Compare Source
configure(Platform)
from the main plugin to modifywhat is getting published. Check out the docs for more details
configureBasedOnAppliedPlugins
DSL method toallow applying the default
configure
logic of the main plugin.configure(Platform)
now validates that the required plugins areapplied (e.g. Android Gradle Plugin for Android projects).
times for Gradle plugin projects with more than one publication. Thanks to
@autonomousapps for the fix.
next release, because the Kotlin/JS plugin has been deprecated.
from
simpleJavadocJar
toplainJavadocJar
. Thanks to @sschuberth.Minimum supported versions
Compatibility tested up to
Configuration cache status
When using Gradle 8.1 or newer configuration cache is generally supported.
Exceptions to that are:
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.
This PR was generated by Mend Renovate. View the repository job log.