-
-
Notifications
You must be signed in to change notification settings - Fork 100
chore: update all dependencies to latest versions #165
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,3 +8,4 @@ | |
| .externalNativeBuild | ||
| .cxx | ||
| firebase-debug.log | ||
| .worktrees/ | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,12 +1,10 @@ | ||
| import dev.androidbroadcast.vbpd.gradle.androidLibraryConfig | ||
| import dev.androidbroadcast.vbpd.gradle.kotlinConfig | ||
| import dev.androidbroadcast.vbpd.gradle.kotlinOptions | ||
| import dev.androidbroadcast.vbpd.gradle.libs | ||
|
|
||
| version = libs.versions.vbpd.get() | ||
| group = "dev.androidbroadcast.vbpd" | ||
|
|
||
| plugins.apply(libs.plugins.jetbrains.kotlin.android.get().pluginId) | ||
| plugins.apply(libs.plugins.android.library.get().pluginId) | ||
| plugins.apply("maven-publish") | ||
| plugins.apply(libs.plugins.vanniktechMavenPublish.get().pluginId) | ||
|
|
@@ -42,11 +40,6 @@ androidLibraryConfig { | |
| targetCompatibility = javaVersion | ||
| } | ||
|
|
||
| kotlinOptions { | ||
| jvmTarget = libs.versions.jvmTarget.get() | ||
| freeCompilerArgs += listOf("-module-name", libraryId) | ||
| } | ||
|
|
||
| testOptions { | ||
| unitTests { | ||
| isIncludeAndroidResources = true | ||
|
Comment on lines
40
to
45
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,26 +1,26 @@ | ||
| [versions] | ||
| android-compileSdk = "35" | ||
| android-buildTools = "35.0.0" | ||
| android-minSdk = "21" | ||
| android-compileSdk = "36" | ||
| android-buildTools = "36.0.0" | ||
| android-minSdk = "23" | ||
| android-targetSdk = "35" | ||
| agp = "8.8.0" | ||
| androidx-activity = "1.10.0" | ||
| androidx-core = "1.15.0" | ||
| agp = "9.1.0" | ||
| androidx-activity = "1.12.4" | ||
| androidx-core = "1.17.0" | ||
| androidx-annotation = "1.9.1" | ||
| androidx-appcompat = "1.7.0" | ||
| androidx-fragment = "1.8.5" | ||
| androidx-appcompat = "1.7.1" | ||
| androidx-fragment = "1.8.9" | ||
| androidx-recyclerview = "1.4.0" | ||
| kotlin = "2.1.10" | ||
| kotlin = "2.3.10" | ||
| vanniktechMavenPublish = "0.30.0" | ||
| jvmTarget = "11" | ||
| jvmTarget = "17" | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 1. jvmtarget set to 17 The version catalog sets jvmTarget to 17, which violates the requirement to keep JVM bytecode/targets at 11. This can cause modules to compile for Java 17, breaking consumers and violating the mandated JVM level. Agent Prompt
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. AGP 9.x requires JVM 17+ — jvmTarget=11 is not compatible with AGP 9. This is not a rule violation, the old value was simply the previous project setting that needed to be updated along with the AGP major upgrade. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Question:AGP 9.x requires JVM 17+ — jvmTarget=11 is not compatible with AGP 9. This is not a rule violation, the old value was simply the previous project setting that needed to be updated along with the AGP major upgrade. Answer:You can reduce/avoid this kind of “false violation” by adding a repository-specific constraint to the agent prompt so it won’t recommend (or insist on) downgrading JVM bytecode targets when AGP 9.x is in use. Add an explicit instruction that:
Suggested config (TOML): [pr_code_suggestions]
extra_instructions = """\
- This repo uses Android Gradle Plugin (AGP) 9.x; therefore Java/Kotlin toolchain and jvmTarget are expected to be 17+.
- Do NOT suggest changing jvmTarget back to 11 just to match historical settings.
- Only raise a “rule/policy violation” if an explicit, authoritative repo policy file (e.g., best_practices.md / compliance checklist / build conventions) states a different required target.
- If there is a conflict (e.g., consumers require 11), present it as a trade-off with options (multi-module targets, toolchains, publishing strategy), not as an unconditional violation.
"""
[pr_reviewer]
extra_instructions = """\
- Treat jvmTarget=17 as acceptable when AGP 9.x is present; avoid calling it a compliance violation unless an explicit repo policy mandates 11.
"""If this feedback is coming from the Relevant Sources:
|
||
| vbpd = "2.0.4" | ||
| detekt = "1.23.8" | ||
| ktlint = "14.0.1" | ||
| kover = "0.9.7" | ||
| robolectric = "4.16.1" | ||
| mockk = "1.14.9" | ||
| androidx-test-core = "1.6.1" | ||
| androidx-test-runner = "1.6.2" | ||
| androidx-test-core = "1.7.0" | ||
| androidx-test-runner = "1.7.0" | ||
| junit = "4.13.2" | ||
|
|
||
| [libraries] | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| sdk=35 |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| sdk=35 |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| sdk=35 |
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.
2. Kotlin jvm target lost
🐞 Bug✓ CorrectnessThe PR removes kotlinOptions { jvmTarget = ... } but does not replace it with Kotlin compilerOptions JVM target configuration, so Kotlin bytecode target is no longer pinned to the repo’s intended jvmTarget=17 while Java is compiled for 17. This can produce mixed classfile targets and can fail builds under stricter Kotlin JVM target validation or when using JVM-17-only bytecode features.Agent Prompt
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation toolsThere 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.
jvmToolchain(17)in Kotlin 1.7+ sets both the JDK toolchain AND thejvmTarget. Additionally, AGP 9's built-in Kotlin aligns the Kotlin target withcompileOptionsJava target. Both are configured to 17 — the Kotlin jvmTarget is not lost.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.
Question:
jvmToolchain(17)in Kotlin 1.7+ sets both the JDK toolchain AND thejvmTarget. Additionally, AGP 9's built-in Kotlin aligns the Kotlin target withcompileOptionsJava target. Both are configured to 17 — the Kotlin jvmTarget is not lost.Answer:
You can mitigate this kind of Gradle/Kotlin false-positive by adding explicit guidance via
extra_instructionsso the model verifies the effective Kotlin bytecode target before flagging “jvmTarget lost”, and treatsjvmToolchain(...)/ AGP alignment as acceptable evidence when applicable.Add this to your repo (wiki/local/global)
.pr_agent.toml:If this issue is being raised by
/reviewrather than/improve, add the same idea there too:To help you iterate, you can run:
/improve --config.output_relevant_configurations=trueto confirm which settings are actually applied.
Relevant Sources: