Anybody else getting a lot of build failures, if y...
# gradle
h
Anybody else getting a lot of build failures, if you/dependabot only bumps one Kotlin plugin to 1.7.20 but keeps another plugins, eg serialization at 1.7.10? That's basically the whole config, beside normal dependencies:
Copy code
plugins {
    kotlin("jvm") version "1.7.20"
    kotlin("plugin.serialization") version "1.7.10"
    id("app.cash.licensee") version "1.5.0"
}

repositories {
    mavenCentral()
}

dependencies {
...
}
Error message:
Copy code
A problem occurred configuring root project 'heimdall'.
26
> Could not resolve all files for configuration ':classpath'.
27
   > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin-api:1.7.20.
28
     Required by:
29
         project : > org.jetbrains.kotlin.jvm:org.jetbrains.kotlin.jvm.gradle.plugin:1.7.20 > org.jetbrains.kotlin:kotlin-gradle-plugin:1.7.20
30
      > Multiple incompatible variants of org.jetbrains.kotlin:kotlin-gradle-plugin-api:1.7.20 were selected:
31
           - Variant org.jetbrains.kotlin:kotlin-gradle-plugin-api:1.7.20 variant gradle70RuntimeElements has attributes {org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.jvm.environment=standard-jvm, org.gradle.jvm.version=8, org.gradle.libraryelements=jar, org.gradle.plugin.api-version=7.0, org.gradle.status=release, org.gradle.usage=java-runtime}
32
           - Variant org.jetbrains.kotlin:kotlin-gradle-plugin-api:1.7.20 variant gradle71RuntimeElements has attributes {org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.jvm.environment=standard-jvm, org.gradle.jvm.version=8, org.gradle.libraryelements=jar, org.gradle.plugin.api-version=7.1, org.gradle.status=release, org.gradle.usage=java-runtime}
33

34
   > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin-api:1.7.20.
35
     Required by:
36
         project : > org.jetbrains.kotlin.jvm:org.jetbrains.kotlin.jvm.gradle.plugin:1.7.20 > org.jetbrains.kotlin:kotlin-gradle-plugin:1.7.20
37
         project : > org.jetbrains.kotlin.jvm:org.jetbrains.kotlin.jvm.gradle.plugin:1.7.20 > org.jetbrains.kotlin:kotlin-gradle-plugin:1.7.20 > org.jetbrains.kotlin:kotlin-gradle-plugin-model:1.7.20
38
      > Multiple incompatible variants of org.jetbrains.kotlin:kotlin-gradle-plugin-api:1.7.20 were selected:
39
           - Variant org.jetbrains.kotlin:kotlin-gradle-plugin-api:1.7.20 variant gradle70RuntimeElements has attributes {org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.jvm.environment=standard-jvm, org.gradle.jvm.version=8, org.gradle.libraryelements=jar, org.gradle.plugin.api-version=7.0, org.gradle.status=release, org.gradle.usage=java-runtime}
40
           - Variant org.jetbrains.kotlin:kotlin-gradle-plugin-api:1.7.20 variant gradle71RuntimeElements has attributes {org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.jvm.environment=standard-jvm, org.gradle.jvm.version=8, org.gradle.libraryelements=jar, org.gradle.plugin.api-version=7.1, org.gradle.status=release, org.gradle.usage=java-runtime
Sure, the "workaround"/solution is easy, just upgrade both plugins in the same PR, but it is a little bit annoying.
c
another workaround is to use renovate bot instead which will combine updates. https://github.com/renovatebot/renovate I think its much better than dependabot
h
Yeah, it is annoying, but unfortunately, it is integrated into GitHub and its security features. Another workaround is to use a variable for the version, which forces dependabot to only create one combined PR too.
247 Views