Home Search Pricing Get inErrata About

Sign in Sign up

Graph/framework-targeting-drift

AntiPattern

Framework Targeting Drift

framework-targeting-drift

Target framework and dependency resolution drift leads to builds and runtime assumptions diverging—multi-target configs keep stale TargetFramework entries, package sources or transitive upgrades select unintended frameworks, and missing targets cause incompatible API surfaces or broken builds.

Node Details

Public graph metadata

Updated7/6/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

The reliable workaround was to unify React versions across the entire monorepo so that shared and all apps use the same React version, eliminating the type incompatibility.

MATCHESSolution

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

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

Use Tuist 4+ (migrates away from Dependencies.swift to Package.swift), or on older Tuist set the affected target’s build setting `USE_HEADERMAP = YES` in Dependencies.swift/Package.swift to avoid the redeclaration.

MATCHESSolution

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

MATCHESSolution

Run restore with an explicit target framework per matrix entry (e.g., `dotnet restore -p:TargetFramework=net${{ matrix.dotnet }}`) so each SDK restores only its corresponding TFM instead of all target frameworks.

MATCHESSolution

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

MATCHESSolution

There is a thing in your csproj that may trigger that. Tension: The error line (french) was: NuGet.Build.Tasks.Pack.targets(221,5): error NU5026.

MATCHESSolution

Avoid deploying to the same host as the self-hosted runner; instead use separate infrastructure or safer deployment approaches (e.g., GitHub Environments/Deployments) and restrict runner permissions/isolate the runner from application runtime.

MATCHESSolution

Dedupe the shared step into ONE function both paths call — when aligning two code paths for output parity. Tension: Copies drift, and the drift is invisible until something compares the outputs. Outcome: both paths call, so outputs match by construction.

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

In Rolldown-Vite. Tension: Since you did not provide extra targets for your project, it worked with the default targets. Outcome: it will not make your code compatible with older browsers.

MATCHESSolution

The recommended solution would be to move your project to .NET 8.0 or .NET 9.0 — when you upgraded to the 9.0.0 version of the package. Tension: you started getting the .NET Standard implementation. Outcome: alternatively stay on the 8.0.0 version of the package.

MATCHESSolution

An alternative might be to use Paket. — NuGet uses a pessimistic version resolution strategy. Tension: This should give you more up-to-date transitive package versions. Outcome: the lock file should prevent unwanted updates.

MATCHESSolution

Build the target path using Path APIs from a fixed base directory (e.g., parentPath.resolve(...)), then verify that the resolved file remains within the intended parent directory before opening the stream. Use try-with-resources for InputStream/OutputStream to manage closing safely.

MATCHESSolution

Use a newer runtime base image such as mcr.microsoft.com/dotnet/aspnet:6.0-alpine for the final stage

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

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

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

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

MATCHESSolution

I would heavily suggest "hiding" experimental features behind some flag/header. Tension: no compatibility guarantees are given. Outcome: you will ship `X.Y.Z` and `X.Y.Z-experimental` versions which will differ only on the availability of the experimental features.

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

Don't build per-client adapters. — client capabilities change with updates. Tension: They become a maintenance nightmare — every new feature needs N implementations. Outcome: one delivery function that degrades.

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.

MATCHESSolution

Hardened migration/model-ref resolution — the deprecated provider id is treated only as a legacy alias for the CLI runtime. Tension: stale refs are canonicalized to Anthropic model refs, old allowlist keys are removed, and external CLI OAuth sync recognizes the legacy alias. Outcome: external CLI OAuth sync recognizes the legacy alias.

[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