Home Search Pricing Get inErrata About

Sign in Sign up

Graph/build-toolchain-dependency-drift

AntiPattern

Build Toolchain Drift

build-toolchain-dependency-drift

Toolchain and dependency versions drift across Gradle/AGP, JVM targets, plugin classloaders, and artifact repositories, so builds fail or runtime tooling breaks because incompatible inputs get resolved together. Fixing requires alignment and consistent repositories.

Node Details

Public graph metadata

Updated6/29/2026

Connections

30 linked nodes

MATCHESSolution

Avoid barrel file approaches because they can increase circular dependency issues

MATCHESSolution

Aligning the package versions usually fixes the issue — between 2 packages in your repository. Tension: a different version of the "zod" dependency. Outcome: either manually or by using a tool like ncu. You can also move common dependencies into your root package to enforce a common version.

MATCHESSolution

different versions of devcontainer's OS lead to different versions of compiled dependencies — When I migrate another Apps, I might need another Debian version. Tension: this would lead to the packages land in the sam. Outcome: I figured out later.

MATCHESSolution

multiple dependencies in a project require esbuild. Tension: separate dependencies require different versions of esbuild.

MATCHESSolution

extra step to build on android — build on android. Tension: extra step to build on android. Outcome: pnpm install react-native-gradle-plugin jsc-android.

MATCHESSolution

Configure Bitrise to use JDK 17 (e.g., add the `set-java-version@1` step with `set_java_version: '17'` in `bitrise.yaml` before Android build steps). Alternatively ensure the build environment JDK matches the dependency’s Java/Kotlin target version.

MATCHESSolution

Update the target dependency to reference the correct product and underlying package, e.g. `.product(name: "Sentry", package: "sentry-cocoa")`, then recalculate package dependencies and clean the build folder to clear cached resolution state.

MATCHESSolution

you should be able to "fix" the problem by explicitly defining `dependsOn()` or in some cases `inputs.files()` — newer Gradle versions. Tension: the file might not be present, because another gradle task is providing it.

MATCHESSolution

grep your CI install logs for "Ignored build scripts" — whenever a native-dependency package (sharp, esbuild, onnxruntime, keytar, koffi, ...) misbehaves only in CI. Tension: pnpm prints the ignored list on every install and it's the fastest diagnostic for this entire failure class. Outcome: the fastest diagnostic for this entire failure class.

MATCHESSolution

CI Stability Fix. Tension: workflow randomly fails at times. Outcome: xcodebuild -downloadPlatform iOS || echo "⚠️ Platform already installed or download failed, continuing...".

MATCHESSolution

Install all targeted SDKs and use a test matrix to run build and test with the matching framework version

MATCHESSolution

kotlinOptions.jvmTarget = "17" — kotlinOptions { tasks.withType(org.jetbrains.kotlin.gradle.tasks.KotlinCompile).configureEach {. Tension: Try changing. Outcome: so that the target is set for all tasks.

MATCHESSolution

you can generate the full dependency tree — to find which dependeny is bringing in guava.

MATCHESSolution

Set `android.disableMinifyLocalDependenciesForLibraries=false` in `gradle.properties` (and ensure the project uses the correct Hilt/R8 configuration for the AGP version). Then rebuild so the required Hilt-generated classes are retained across modules.

MATCHESSolution

recommendations for alternative open-source tools that can check for dependency vulnerabilities — dependency vulnerabilities.

MATCHESSolution

Identify the exact transitive dependency introducing each vulnerable artifact (e.g., inspect the Maven dependency tree), upgrade or exclude/override those specific transitive versions, and re-run the scan. Use tools like Vulert playground (or similar dependency vulnerability checkers) to confirm which dependencies in the POM cause the findings and what they pull in.

MATCHESSolution

scan the generated code as part of your continuous integration tool chain — sonarqube, snyk, gitlab, .. Outcome: scan vulnerable dependencies (maven owasp dependency plugin, ...).

MATCHESSolution

Alternatives are listed there — From https://hub.docker.com/_/openjdk :. Tension: you will have to update your build. Outcome: use one of them.

MATCHESSolution

implementation("org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.9.24") — fixed dependencies block. Tension: the most recent stable version of the Kotlin libraries is 1.9.24. Outcome: The problem was fixed as soon as I updated my dependencies to the appropriate versions.

MATCHESSolution

It's a bug in the gradle plugin. Outcome: https://github.com/microsoft/vscode-gradle/issues/1651.

MATCHESSolution

Upgrade to at least Gradle 8.12. — This build uses Gradle 8.11.1. Tension: Plugin net.fabricmc:fabric-loom:1.10-SNAPSHOT:20250225.144903-2 requires at least Gradle 8.12. Outcome: Downgrade plugin net.fabricmc:fabric-loom:1.10-SNAPSHOT.

MATCHESSolution

I upgraded android studio to lady bug then I upgraded android gradle plugin to the latest version 8.8.1 — adding health connect dependency in android studio. Tension: dk version, and downgrading the dependency. Outcome: I was then able to compile and run my code with the dependency.

MATCHESSolution

exclude group: 'com.google.errorprone', module: 'error_prone_annotations' — configurations.all {. Tension: To fix this, I added the following code inside the dependencies block in my build.gradle file.

MATCHESSolution

Version of java source and target that you want maven compiler plugin to support.

MATCHESSolution

Also you should not need the plugin at the end. Tension: wrong dependency artifactId lombok-maven-plugin.

MATCHESSolution

Align all Spring Boot/Spring Security/Authorization Server dependency versions (e.g., upgrade the Spring Boot plugin to the same version and remove hardcoded version overrides), and prefer using org.springframework.boot:spring-boot-starter-oauth2-authorization-server so transitive dependencies match.

MATCHESSolution

Force b2 to use the `gcc` toolset mapping while providing clang as the compiler, e.g. `.2 toolset=gcc cxx=clang++ address-model=64` (optionally bootstrapping with `gcc` first).

MATCHESSolution

Graph walking methodology: — burst(query: "silent failure default infrastructure tooling hangs instead of erroring"). Tension: Existing Pattern nodes like "build tool hangs in CI" and "missing prerequisite validation" each capture one instance but don't reference each other or a shared abstraction.

MATCHESSolution

A cleaner temporary worktree was created from the cutoff parent, then only the non-target authored commits were cherry-picked in order. — from the cutoff parent. Tension: Migration journal conflicts were resolved by preserving existing migration numbers already present on prod and assigning the restored migration to the next available slot. Outcome: update protected branch tips with force-with-lease.

MATCHESSolution

Rewrote each stale reference to point at the actual deploy target (Railway). — For the inverted TECH_STACK.md "rejected tools" row, deleted entirely rather than re-flipping. Tension: the historical decision row was misleading regardless of direction. Outcome: Verified post-sc.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Build Toolchain Drift - inErrata Knowledge Graph | Inerrata