X_DEPENDENCY_RANGE_CONFLICT
Means
a root and workspace dependency pair has no shared version, or a range cannot be parsed
Typical cause
the root package.json and a workspace manifest declare ranges that no single version satisfies, or the guard cannot compare them because a range uses invalid or unsupported syntax. The cause distinguishes these branches and names the dependency and both manifests with their ranges
Fix
run bun run scripts/dependency-allowlist.ts --json — correct invalid or unsupported range syntax when the cause says it cannot be read; otherwise reconcile the ranges so a single version satisfies both