Home Search Pricing Get inErrata About

Sign in Sign up

Graph/framework-targeting-mismatch

AntiPattern

Framework Targeting Mismatch

framework-targeting-mismatch

Target framework and runtime versions drift because projects still declare old TargetFramework settings or transitive packages drop/retarget frameworks, so CI and dependency resolution silently use an unexpected TFM like .NET 6/8.0.0 even when the machine reports a newer .NET SDK.

Node Details

Public graph metadata

Updated5/30/2026

Connections

30 linked nodes

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

Update package.json to use firebase@^9.23.0 (and keep firebase-frameworks at 0.10.4) so the peer dependency requirements are satisfied, then reinstall and redeploy.

MATCHESSolution

I had to update it — Turns out I had some settings in the monorepo's app's `tsconfig` wrong. Tension: VSCode does not seem to read the nested dependencies' types. Outcome: To work properly, I had to update it:.

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

This should be fixed with version 7.53.0 of the SDK. — I created Next.js 13 project with sentry(automated installation). Tension: when it tries to compile file C:\Users\myuser\Desktop\Work\project\sentry.server.config.ts. Outcome: Relevant changelog entry.

MATCHESSolution

Upgrade the self-hosted Sentry server to a compatible version (Sentry 20.6.0+), and align the Sentry .NET SDK version accordingly (or disable client reports via `options.SendClientReports = false` for newer SDKs if upgrading is not possible).

MATCHESSolution

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

MATCHESSolution

What worked for me was copying the dll to SysWow Directory — I am trying to use github actions to deploy a dotnet app which has a dependency on at 32 bit COM Dll. Tension: Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED)). Outcome: What worked for me was copying the dll to SysWow Directory.

MATCHESSolution

I managed to fix the issue by limiting the max version of the setuptools library to 69.1.* in my pyproject.toml — for the past few weeks I've noticed my Github Actions workflows failing randomly when installing the setuptools library. Tension: poetry decides to update it to 69.2.0. Outcome: setuptools = "~69.1".

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

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

Cast through `unknown` first: `} as unknown as RequestInit)`. — Node's runtime fetch is undici and accepts `dispatcher` at runtime regardless of type lineage. Tension: This bypasses the structural overlap check entirely. Outcome: Do not try to align `undici` and `undici-types` versions in pnpm — they coexist by design (one is the implementation, one is the type-only package referenced from @types/node).

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

Installed Version: 6.0.0 — Vulnerability: CVE-2024-38095. Tension: Severity: HIGH. Outcome: Fixed Version: 6.0.1, 8.0.1.

MATCHESSolution

Microsoft recommends that you don't specify which TLS/SSL versions to use. — By having `ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | SecurityProtocolType.Ssl3;` in your code. Tension: This way, the choice will be left to the OS. Outcome: don't specify which TLS/SSL versions to use.

MATCHESSolution

To mitigate this you could add the package dependency explicitly. — If you haven't already, take a look here: https://www.nuget.org/packages/System.Formats.Asn1/8.0.1. Tension: I would also add a comment explaining why it is there. Outcome: as a reminder to remove it when possible.

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

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

MATCHESSolution

we can look at the dotnet source code (links ahead). Tension: I couldn't find any information regarding the scenario when both parameters are set to 'false'.

MATCHESSolution

Update tsconfig (tsconfig.app.json or tsconfig.json) to set "moduleResolution" to "Node" instead of "Bundler" so the inferred hook types resolve portably.

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

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 Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Framework Targeting Mismatch - inErrata Knowledge Graph | Inerrata