Home Search Pricing Get inErrata About

Sign in Sign up

Graph/dependency-toolchain-drift

Pattern

Dependency and Toolchain Drift

dependency-toolchain-drift

Mismatched dependency artifacts and build toolchains drift across upgrades (e.g., iOS 17, Xcode version, Gradle plugin/JVM targets) so Gradle can’t resolve packages or compiles fail due to incompatible JVM targets.

Node Details

Public graph metadata

Updated7/6/2026

Connections

30 linked nodes

Type instantiation is excessively deep and possibly infinite — in a monorepo/workspace project. Tension: on seemingly benign types like this. Outcome: I've found this is almost always due to a mismatched dependency between 2 packages in your repository.

When publishing the Vite-built package, the generated dist output includes internal build artifacts such as node_modules/_virtual and/or breaks dependency resolution because subpath imports like react/jsx-runtime aren’t treated as externals. This results in unwanted contents being packaged and incorrect bundling for NPM publication.

Deploying to Vercel fails to apply the desired npm install flags (e.g., `--legacy-peer-deps`), causing dependency/peer conflicts during deployment.

Bitrise Android release builds fail at `:package_info_plus:compileReleaseJavaWithJavac` with `error: invalid source release: 17`. The same project builds locally in release/development.

Zone mismatch. — during runApp. Tension: The Flutter bindings were initialized in a different zone than is now being used. Outcome: This will likely cause confusion and bugs as any zone-specific configurat.

The workflow randomly fails at times with errors such as. Tension: iOS 18.0 is not installed. To use with Xcode, first download and install the platform.

I get an error related to my third party frameworks (Firebase and others) added via SPM. — the app builds and archives fine locally but from GitHub action is produces errors. Tension: I've tried various combinations of arguments for xcode build but without success.

Tension: Please build with a newer iOS SDK. Outcome: I fixed it:.

Execution failed for task ':app:mergeReleaseJavaResource'. — In the Run Gradlew step in expo. Tension: 2 files found with path 'org/bouncycastle/pqc/crypto/picnic/lowmcL5.bin.properties' from inputs. Outcome: Adding a packaging block may help.

Inconsistent JVM-target compatibility detected for tasks 'compileDebugJavaWithJavac' (1.8) and 'compileDebugKotlin' (17). Tension: Execution failed for task ':stripe_android:compileDebugKotlin'. Outcome: BUILD FAILED in 14s.

The app build fails with errors about missing classes generated by Dagger Hilt when Proguard/R8 minification is enabled. Existing Hilt Proguard rules do not prevent the missing generated classes.

Adding nondeterministic compilation breaks reproducible builds — users will no longer be able to verify the packages they install. Tension: this security measure is a good example of so-called security theater. Outcome: it will not provide additional security for most of the cases, but will greatly complicate a lot of things.

you are going to get a change request — if you don't keep your front-end dependencies up-to-date after a year or two. Tension: that will require you to upgrade an existing dependency for compatibility, that will break 5 other things. Outcome: you won't be able to modify them without declaring package.json bankruptcy and starting over.

Azure defender or qualys flags it as present — after excluding the dependency and adding it exclusively. Tension: that confirms that the dependency is coming from some fat jar that is not visible via mvn dependency:tree neither by any IDE. Outcome: I want to know if there is any way we can view all the dependencies inside fat jars included in the project.

OWASP dependency scanning reports critical vulnerabilities in Maven dependencies used by a Java Jersey application, even after upgrading to latest versions. The scan output also includes artifacts whose provenance in the project is unclear (e.g., kerb-server).

The project’s dependency tree includes the vulnerable `inflight@1.0.6` library (deduped) via transitive dependencies of Angular build/CLI tooling, and the user needs to mitigate the vulnerability without migrating to Angular 16.

On a freshly-provisioned GCP project. Tension: You fix one, redeploy, and hit the next. This burns a lot of time if you don't know the chain up front. Outcome: each at a different stage.

Gradle builds the project, but the annotation processor does not run

Could not find org.jetbrains.kotlin:kotlin-stdlib-jdk11:2.2.0. — Execution failed for task ':app:checkDebugAarMetadata'. Tension: Could not resolve all files for configuration ':app:debugRuntimeClasspath'. Outcome: I was attempting to use the `kotlin-stdlib-jdk11` library, version 2.0.20, which does not exist, my build was failing.

I'm upgrading a Vaadin 23.2 app to Vaadin 24.8. I have a compilation error on one of my components. Tension: IntelliJ IDEA doesn't show any error, but Gradle compilation (JDK17) throws. Outcome: when I remove the class the issue is gone.

Opening the Flutter project in VS Code fails with a Gradle build error stating the toolchain at '/usr/lib/jvm/java-21-openjdk' does not provide the required capability 'JAVA_COMPILER' for compiling Android test Java sources.

Error running 'Main'. Tension: com.android.tools.idea.gradle.dcl.lang.DeclarativeParserDefinition PluginClassLoader. Outcome: com.android.tools.idea.gradle.dcl.lang.DeclarativeParserDefinition PluginClassLoader(plugin=PluginDescriptor(name=Gradle Declarative Support, id=com.android.tools.gradle.dcl, descriptorPath=plugin.xml, path=~/bin/intellij/plugins/android-gradle-declarative-lang-ide, version=251.23774.435, package=null, isBundled=true), packagePrefix=null, state=active, parents=PluginDescriptor(name=Kotlin, id=org.jetbrains.kotlin, descriptorPath=plugin.xml, path=~/bin/intellij/plugins/Kotlin, version=251.23774.435-IJ, package=org.jetbrains.kotlin, isBundled=true), PluginDescriptor(name=Gradle, id=com.intell.

Plugin net.fabricmc:fabric-loom:1.10-SNAPSHOT:20250225.144903-2 requires at least Gradle 8.12. — A problem occurred configuring root project 'projectname'. Tension: This build uses Gradle 8.11.1.

Android Studio (Ladybug 24.2.1) is using JDK 21 by default, but the user needs JDK 17 to be used for both Android Studio and the Android toolchain. They want to change the IDE JDK from 21 to 17.

Fatal error compiling: error: release version 21 not supported — mvn clean package -Pstaging -e. Outcome: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile.

a lot of build targets of `leveldb` tests were added too — After adding `leveldb` as dependency of my project. Tension: causing a long list of undesired information while building. Outcome: logs are flooded by `leveldb` build targets like below.

Building Boost with b2 using the clang toolset on Windows produces static libraries as .lib files instead of the .a files generated when building with gcc toolset.

This created drift between human install docs, machine-readable agent manifests, llms.txt references, and actual tested client behavior.

Features built on optional capabilities silently degrade across the client matrix. Outcome: Community 4's transport bugs and Community 103's capability detection failures are two symptoms of the same architectural constraint.

A plugin package needed a tracked .mcp.json despite repository/global ignore rules — plugin package. Tension: plus regression coverage asserting the config shape.

[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