Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

package.json (1)

43-58: ⚠️ Potential issue | 🔴 Critical

Lockfile must match manifest bumps before merge.

Line 43-Line 58 updates manifest versions and packageManager; ensure pnpm-lock.yaml is regenerated with pnpm 10.30.3 and committed. This is the same blocker previously reported.

#!/bin/bash
set -euo pipefail

test -f package.json
test -f pnpm-lock.yaml

python - <<'PY' > /tmp/expected_specs.txt
import json
deps = [
  "@biomejs/biome",
  "@types/node",
  "@vitest/coverage-v8",
  "cspell",
  "lint-staged",
  "prettier",
  "sort-package-json",
  "tsdown",
  "vitest",
]
pkg = json.load(open("package.json"))
for d in deps:
  print(f"{d}@{pkg['devDependencies'][d]}")
print(f"packageManager={pkg['packageManager']}")
PY

while IFS= read -r spec; do
  if rg -n --fixed-strings "$spec" pnpm-lock.yaml >/dev/null; then
    echo "OK   $spec"
  else
    echo "MISS $spec"
  fi
done < /tmp/expected_specs.txt

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 43 - 58, The package manifest was updated
(devDependencies like "@biomejs/biome", "@types/node", "@vitest/coverage-v8",
"cspell", "lint-staged", "prettier", "sort-package-json", "tsdown", "vitest" and
packageManager) but pnpm-lock.yaml was not regenerated; run pnpm using the
declared packageManager version ([email protected]) to regenerate the lockfile (e.g.,
pnpm install or pnpm -w install if workspace), ensure pnpm-lock.yaml now
contains entries matching the new devDependency versions and
[email protected], and commit the updated pnpm-lock.yaml alongside the
package.json change.

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

package.json (1)

43-58: ⚠️ Potential issue | 🔴 Critical

Lockfile is out of sync with updated deps (merge blocker).

CI already reports mismatches for these updated entries. Regenerate and commit pnpm-lock.yaml using [email protected] so Lines 43-58 are reflected.

#!/bin/bash
set -euo pipefail

test -f package.json
test -f pnpm-lock.yaml

python - <<'PY'
import json
with open("package.json") as f:
    pkg=json.load(f)
targets=[
  "@biomejs/biome","@types/node","@vitest/coverage-v8",
  "cspell","lint-staged","prettier","sort-package-json","tsdown","vitest"
]
for t in targets:
    print(f"{t}@{pkg['devDependencies'][t]}")
print("packageManager="+pkg["packageManager"])
PY

echo "--- lockfile hits ---"
python - <<'PY' | while read -r spec; do
import json
with open("package.json") as f:
    pkg=json.load(f)
targets=[
  "@biomejs/biome","@types/node","@vitest/coverage-v8",
  "cspell","lint-staged","prettier","sort-package-json","tsdown","vitest"
]
for t in targets:
    print(f"{t}@{pkg['devDependencies'][t]}")
PY
  rg -n --fixed-strings "$spec" pnpm-lock.yaml >/dev/null && echo "✓ $spec" || echo "✗ $spec"
done

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 43 - 58, The pnpm lockfile is out of sync with the
devDependencies (entries like `@biomejs/biome`, `@types/node`, `@vitest/coverage-v8`,
cspell, lint-staged, prettier, sort-package-json, tsdown, vitest) and the
packageManager field; regenerate pnpm-lock.yaml using [email protected] so the lock
reflects package.json, verify the lock contains those exact spec strings, and
commit the updated pnpm-lock.yaml and any lockfile metadata changes (ensuring
packageManager remains [email protected]).

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

package.json (1)

58-58: 🧹 Nitpick | 🔵 Trivial

Align engines.pnpm with the pinned packageManager version.

Line 58 pins [email protected], but Line 61 still allows >=10.17.1, which permits older clients and version drift.

Proposed diff

   "engines": {
     "node": ">=22.14.0",
-    "pnpm": ">=10.17.1"
+    "pnpm": ">=10.30.3"
   },

#!/bin/bash
set -euo pipefail

python - <<'PY'
import json, re

def parse(v):
    return tuple(int(x) for x in v.split("."))

with open("package.json", "r", encoding="utf-8") as f:
    d = json.load(f)

pm = d.get("packageManager", "")
eng = d.get("engines", {}).get("pnpm", "")

m_pm = re.match(r"^pnpm@(\d+\.\d+\.\d+)$", pm)
m_eng = re.match(r"^>=\s*(\d+\.\d+\.\d+)$", eng)

print("packageManager:", pm)
print("engines.pnpm :", eng)

if not (m_pm and m_eng):
    print("Could not parse one or both fields.")
else:
    pm_v = m_pm.group(1)
    eng_v = m_eng.group(1)
    aligned = parse(eng_v) >= parse(pm_v)
    print("packageManager version:", pm_v)
    print("engines floor        :", eng_v)
    print("aligned              :", aligned)
PY

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 58, package.json currently pins packageManager to
"[email protected]" but engines.pnpm still allows ">=10.17.1"; update the
engines.pnpm field to at least ">=10.30.3" (or exactly "10.30.3" if you prefer a
strict pin) so the engines.pnpm floor aligns with the packageManager value,
ensuring the version strings in the packageManager and engines.pnpm fields match
and use the same semver format.

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

package.json (1)

43-58: ⚠️ Potential issue | 🔴 Critical

Lockfile is still out of sync with updated dependency specifiers.

Lines 43-58 changed multiple devDependencies and packageManager, and CI is already failing pnpm install --frozen-lockfile for specifier mismatch. Please regenerate and commit pnpm-lock.yaml using pnpm 10.30.3 before merge.

#!/bin/bash
set -euo pipefail

python - <<'PY' > /tmp/expected_specs.txt
import json
d = json.load(open("package.json"))
keys = [
  "@biomejs/biome",
  "@types/node",
  "@vitest/coverage-v8",
  "cspell",
  "lint-staged",
  "prettier",
  "sort-package-json",
  "tsdown",
  "vitest",
]
for k in keys:
  print(f"{k}@{d['devDependencies'][k]}")
print(d["packageManager"])
PY

echo "Checking expected specs in pnpm-lock.yaml..."
while IFS= read -r spec; do
  if rg -n --fixed-strings "$spec" pnpm-lock.yaml >/dev/null; then
    echo "FOUND   $spec"
  else
    echo "MISSING $spec"
  fi
done < /tmp/expected_specs.txt

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 43 - 58, The pnpm lockfile is out of sync with the
updated devDependencies and packageManager in package.json: update
pnpm-lock.yaml by running pnpm using the specified packageManager version
([email protected]) so the specifiers for the devDependencies (e.g.,
"@biomejs/biome", "@types/node", "@vitest/coverage-v8", "cspell", "lint-staged",
"prettier", "sort-package-json", "tsdown", "vitest") and the packageManager
entry are reflected in the lockfile, then commit the regenerated pnpm-lock.yaml
so CI no longer fails `pnpm install --frozen-lockfile`.

package.json (1)

58-58: ⚠️ Potential issue | 🔴 Critical

Lockfile still out of sync.

Pipeline fails with lockfile mismatch. Run pnpm install and commit pnpm-lock.yaml.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 58, The repository's pnpm lockfile is out of sync with
package.json's packageManager setting; run `pnpm install` locally to
regenerate/update pnpm-lock.yaml, verify the lockfile changes, and commit the
updated pnpm-lock.yaml alongside the package.json change so the pipeline's
lockfile check passes (refer to the "packageManager" field and ensure
pnpm-lock.yaml is included in the commit).

package.json (1)

43-58: ⚠️ Potential issue | 🔴 Critical

Lockfile is out of sync with manifest changes (CI blocker).

Line 43-58 updates dependency specifiers and packageManager, and CI already reports specifier mismatches. Regenerate and commit pnpm-lock.yaml from this branch before merge.

#!/bin/bash
set -euo pipefail

python - <<'PY' > /tmp/updated-specs.txt
import json
d = json.load(open("package.json"))
for name in [
  "@biomejs/biome",
  "@types/node",
  "@vitest/coverage-v8",
  "cspell",
  "lint-staged",
  "prettier",
  "sort-package-json",
  "tsdown",
  "vitest",
]:
    print(f"{name}@{d['devDependencies'][name]}")
PY

echo "Checking whether updated specs are present in pnpm-lock.yaml..."
while IFS= read -r spec; do
  if rg -n --fixed-strings "$spec" pnpm-lock.yaml >/dev/null; then
    echo "✓ $spec"
  else
    echo "✗ missing: $spec"
  fi
done < /tmp/updated-specs.txt

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 43 - 58, The lockfile is out of sync with the
manifest changes: regenerate pnpm-lock.yaml so the updated devDependency
specifiers (e.g. "@biomejs/biome", "@types/node", "@vitest/coverage-v8",
"cspell", "lint-staged", "prettier", "sort-package-json", "tsdown", "vitest",
and others shown in package.json) and the packageManager value
("packageManager": "[email protected]") are reflected in the lockfile; run the
appropriate pnpm command to update the lockfile (e.g. pnpm install or pnpm
install --lockfile-only with [email protected]), verify pnpm-lock.yaml contains the
new specifiers, and commit the updated pnpm-lock.yaml to this branch before
merging.

package.json (1)

43-58: ⚠️ Potential issue | 🔴 Critical

Lockfile is out of sync with the updated specs (merge blocker).

CI already reports 9 specifier mismatches after these version bumps. Regenerate pnpm-lock.yaml with pnpm 10.30.3 and commit it with this PR.

#!/bin/bash
set -euo pipefail

python - <<'PY' | while read -r spec; do
import json
data = json.load(open("package.json"))
for p in [
  "@biomejs/biome",
  "@types/node",
  "@vitest/coverage-v8",
  "cspell",
  "lint-staged",
  "prettier",
  "sort-package-json",
  "tsdown",
  "vitest",
]:
  print(f"{p}@{data['devDependencies'][p]}")
PY
  if rg -n --fixed-strings "$spec" pnpm-lock.yaml >/dev/null 2>&1; then
    echo "OK  $spec"
  else
    echo "MISS $spec"
  fi
done

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 43 - 58, The pnpm lockfile is out of sync with the
bumped devDependencies in package.json (see packageManager "[email protected]" and
the devDependencies like "@biomejs/biome", "@types/node", "@vitest/coverage-v8",
"cspell", "lint-staged", "prettier", "sort-package-json", "tsdown", "vitest");
regenerate pnpm-lock.yaml using pnpm 10.30.3 (e.g. run pnpm install with that
pnpm binary or use pnpm env to ensure version), verify the nine specifier
mismatches are resolved, and commit the updated pnpm-lock.yaml to the PR so CI
no longer reports missing specs.

package.json (1)

43-58: ⚠️ Potential issue | 🔴 Critical

Commit the matching pnpm-lock.yaml.

Lines 43-58 change package specifiers and the pinned pnpm version, and CI is already reporting a manifest/lockfile mismatch. Regenerate pnpm-lock.yaml with pnpm 10.31.0 and include it in this PR.

#!/bin/bash
set -euo pipefail

python - <<'PY'
import json
import subprocess
import sys

try:
    import yaml
except ImportError:
    subprocess.check_call([sys.executable, "-m", "pip", "install", "-q", "pyyaml"])
    import yaml

with open("package.json") as f:
    pkg = json.load(f)
with open("pnpm-lock.yaml") as f:
    lock = yaml.safe_load(f)

root = lock.get("importers", {}).get(".", {})
lock_specs = {}
for section in ("dependencies", "devDependencies", "optionalDependencies"):
    for name, meta in root.get(section, {}).items():
        lock_specs[name] = meta.get("specifier") if isinstance(meta, dict) else meta

targets = [
    "@biomejs/biome",
    "@types/node",
    "@vitest/coverage-v8",
    "cspell",
    "lint-staged",
    "prettier",
    "sort-package-json",
    "tsdown",
    "vitest",
]

failed = False
for name in targets:
    manifest_version = pkg["devDependencies"][name]
    lockfile_version = lock_specs.get(name)
    ok = manifest_version == lockfile_version
    print(f'{"OK" if ok else "MISMATCH"} {name}: manifest={manifest_version} lockfile={lockfile_version}')
    failed |= not ok

sys.exit(1 if failed else 0)
PY

Expected result: every line prints OK. If not, the lockfile still needs regeneration.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 43 - 58, The package manifest and pinned
packageManager were changed but the pnpm lockfile is out of sync; regenerate
pnpm-lock.yaml using [email protected] (as set in the packageManager field) so the
specifiers for the devDependencies (e.g., "@biomejs/biome", "@types/node",
"@vitest/coverage-v8", "cspell", "lint-staged", "prettier", "sort-package-json",
"tsdown", "vitest") match the lockfile, then add the updated pnpm-lock.yaml to
the PR and re-run CI to verify no manifest/lockfile mismatches.

package.json (1)

43-58: ⚠️ Potential issue | 🔴 Critical

Regenerate pnpm-lock.yaml with the pinned pnpm version.

CI is already failing pnpm install --frozen-lockfile because these specifiers no longer match the lockfile. Commit the refreshed pnpm-lock.yaml alongside this manifest update.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 43 - 58, Update the lockfile to match the pinned
package manager by regenerating pnpm-lock.yaml after changing the packageManager
entry ("packageManager": "[email protected]"); run pnpm install using that pnpm
version (e.g., install with [email protected] or run pnpm install --frozen-lockfile
locally after switching to that pnpm) and commit the updated pnpm-lock.yaml
alongside the package.json change so CI passes.

package.json (1)

58-61: 🧹 Nitpick | 🔵 Trivial

Consider aligning engines.pnpm floor with Line 58 packageManager.
Keeping engines.pnpm at >=10.17.1 while pinning [email protected] can allow local/CI drift.

#!/bin/bash
set -euo pipefail

python - <<'PY'
import json
d = json.load(open("package.json"))
print("packageManager:", d.get("packageManager"))
print("engines.pnpm :", d.get("engines", {}).get("pnpm"))
PY

Proposed diff

   "engines": {
     "node": ">=22.14.0",
-    "pnpm": ">=10.17.1"
+    "pnpm": ">=10.32.1"
   },

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 58 - 61, The package.json currently pins
packageManager to "[email protected]" but leaves "engines.pnpm" at ">=10.17.1", which
can cause local/CI drift; update the engines.pnpm value to match the
packageManager floor (e.g., ">=10.32.1") or otherwise align it with the pinned
version so both packageManager and engines.pnpm reference the same minimum pnpm
version; change the engines entry for pnpm accordingly where "packageManager"
and "engines" are defined.

package.json (1)

43-58: ⚠️ Potential issue | 🔴 Critical

Lockfile is out of sync with these manifest changes (merge blocker).

Line 43-Line 58 update dependency specifiers and packageManager, but CI already reports 9 manifest/lockfile mismatches. Regenerate and commit pnpm-lock.yaml using the pinned toolchain ([email protected]).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 43 - 58, The package manifest was changed (updated
dependency specifiers like "@biomejs/biome", "@types/node", "prettier",
"typescript", "vitest", etc. and the "packageManager" field) but the pnpm
lockfile is out of sync; regenerate pnpm-lock.yaml using the pinned toolchain
[email protected] by running the exact pnpm binary (e.g., install using [email protected]
or npx [email protected]) and running pnpm install to update pnpm-lock.yaml, then
commit the updated pnpm-lock.yaml alongside the package.json changes.

package.json (1)

58-61: 🧹 Nitpick | 🔵 Trivial

Align engines.pnpm floor with pinned packageManager.

Line 58 pins [email protected], but Line 61 still allows >=10.17.1. Raising the floor reduces local/CI drift while keeping an open upper bound.

Proposed diff

   "engines": {
     "node": ">=22.14.0",
-    "pnpm": ">=10.17.1"
+    "pnpm": ">=10.32.1"
   },

#!/bin/bash
set -euo pipefail

python - <<'PY'
import json, re
with open("package.json") as f:
    pkg = json.load(f)

pm = pkg.get("packageManager", "")
eng = pkg.get("engines", {}).get("pnpm", "")
m = re.search(r"pnpm@(\d+\.\d+\.\d+)", pm)

print("packageManager:", pm)
print("engines.pnpm:", eng)
if m and eng.startswith(">="):
    print("pinned pnpm:", m.group(1))
    print("engine floor:", eng[2:])
PY

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 58 - 61, The engines.pnpm floor is out of sync
with the pinned packageManager value; update the "engines". "pnpm" entry to
match the pinned version in "packageManager" (change the value from ">=10.17.1"
to ">=10.32.1") so the minimum allowed pnpm version aligns with the pinned
[email protected]; ensure you only adjust the floor (keep the ">=" form) in the
package.json fields "packageManager" and "engines"."pnpm".

package.json (1)

43-58: ⚠️ Potential issue | 🔴 Critical

Lockfile is out of sync with updated specifiers (merge blocker).

Lines 43–58 changed dependency specifiers and packageManager, and CI already fails frozen install on manifest/lockfile mismatch. Regenerate and commit pnpm-lock.yaml using pnpm 10.32.1, then re-run CI.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 43 - 58, The package manifest was changed
(dependency specifiers and packageManager) but pnpm-lock.yaml wasn’t updated;
run [email protected] to regenerate the lockfile, e.g. install with the pinned
packageManager (pnpm 10.32.1) so pnpm-lock.yaml is rewritten, commit the updated
pnpm-lock.yaml alongside the package.json changes, and push so CI’s frozen
install succeeds and the build can be re-run for verification.

package.json (1)

43-58: ⚠️ Potential issue | 🔴 Critical

Lockfile is out of sync with updated specifiers (merge blocker).

Line 43-58 changes dependency/package-manager specifiers, and CI already fails on frozen install due to specifier mismatch. Commit an updated pnpm-lock.yaml generated with the pinned pnpm version.

#!/bin/bash
set -euo pipefail

echo "Checking packageManager pin:"
node -e 'const p=require("./package.json"); console.log(p.packageManager)'

echo "Checking lockfile mismatch via pnpm frozen resolution:"
pnpm install --frozen-lockfile --ignore-scripts

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 43 - 58, The package.json change updated
dependency specifiers and the packageManager field (packageManager) but the pnpm
lockfile is not updated, causing CI failures on frozen installs; regenerate and
commit an updated pnpm-lock.yaml using the pinned pnpm version ([email protected]) so
the lockfile matches the new specifiers and packageManager field—run pnpm
install with that pnpm to produce the updated pnpm-lock.yaml, verify pnpm
install --frozen-lockfile passes, and include the new pnpm-lock.yaml in the
commit.

package.json (2)

58-61: 🧹 Nitpick | 🔵 Trivial

Align engines.pnpm with pinned packageManager.

packageManager now pins [email protected], but engines.pnpm still allows >=10.17.1. Consider raising the floor to reduce local/CI version drift.

Proposed diff

   "engines": {
     "node": ">=22.14.0",
-    "pnpm": ">=10.17.1"
+    "pnpm": ">=10.32.1"
   },

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 58 - 61, The package.json currently pins
"packageManager": "[email protected]" but the engines block still allows "pnpm":
">=10.17.1"; update the engines.pnpm entry to match the pinned manager (e.g.,
">=10.32.1") so local/CI pnpm versions align with the packageManager. Modify the
engines object (engines.pnpm) accordingly and run a quick install/check to
verify no CI/tooling warnings.

---

43-58: ⚠️ Potential issue | 🔴 Critical

Lockfile is out of sync with these dependency bumps (merge blocker).

pnpm install --frozen-lockfile is failing due to specifier mismatches for the updated deps. Regenerate and commit pnpm-lock.yaml with pnpm 10.32.1 before merge.

#!/bin/bash
set -euo pipefail

python - <<'PY' > /tmp/expected-specs.txt
import json
deps = [
  "@biomejs/biome",
  "@types/node",
  "@vitest/coverage-v8",
  "cspell",
  "lint-staged",
  "prettier",
  "sort-package-json",
  "tsdown",
  "vitest",
]
p = json.load(open("package.json"))
for d in deps:
  print(f"{d}@{p['devDependencies'][d]}")
PY

while read -r spec; do
  if rg -n --fixed-strings "$spec" pnpm-lock.yaml >/dev/null; then
    echo "OK   $spec"
  else
    echo "MISS $spec"
  fi
done < /tmp/expected-specs.txt

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 43 - 58, The lockfile is out of sync with the
bumped devDependencies listed in package.json (see packageManager/[email protected]);
fix it by regenerating pnpm-lock.yaml using pnpm v10.32.1 (install that pnpm
version if needed), run pnpm install to update pnpm-lock.yaml, verify the new
lockfile satisfies the specifiers (e.g., the deps like `@biomejs/biome`,
`@types/node`, `@vitest/coverage-v8`, cspell, prettier, vitest), then commit the
updated pnpm-lock.yaml and push; after committing, run pnpm install
--frozen-lockfile (or the provided verification script) to confirm no specifier
mismatches remain.

package.json (2)

53-53: ⚠️ Potential issue | 🟠 Major

Migrate tsdown configs for v0.21 breaking changes.

v0.21.0 renames external → deps.neverBundle and noExternal → deps.alwaysBundle. Update affected configs in packages/convert/ and packages/reactivity/.

#!/bin/bash
# Check if tsdown configs still use old 'external' key
rg -n '"external"\s*:' packages/convert/tsdown.config.ts packages/reactivity/tsdown.config.ts || echo "✓ Already migrated or not using external"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 53, The tsdown upgrade to v0.21 requires migrating old
config keys: open packages/convert/tsdown.config.ts and
packages/reactivity/tsdown.config.ts, find any occurrences of the old "external"
and "noExternal" keys and replace them with the new shape under deps (map
"external" → deps.neverBundle and "noExternal" → deps.alwaysBundle), preserving
the existing arrays/values; validate the config object shape so deps is present
and contains neverBundle/alwaysBundle arrays; run the provided ripgrep check to
confirm no remaining "external" keys.

---

58-61: 🧹 Nitpick | 🔵 Trivial

Align engines.pnpm with packageManager.

packageManager pins [email protected] but engines.pnpm allows >=10.17.1. Update to >=10.32.1 to prevent local/CI drift.

Proposed diff

   "engines": {
     "node": ">=22.14.0",
-    "pnpm": ">=10.17.1"
+    "pnpm": ">=10.32.1"
   },

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 58 - 61, The package.json currently pins
packageManager to "[email protected]" but engines.pnpm permits ">=10.17.1", causing
potential local/CI drift; update the engines.pnpm value to ">=10.32.1" so it
matches the packageManager pin (edit the engines block entry "pnpm" in
package.json to the new minimum).

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

package.json (1)

43-58: ⚠️ Potential issue | 🔴 Critical

Lockfile is still out of sync (merge blocker).

CI already fails with ERR_PNPM_OUTDATED_LOCKFILE for the versions changed on Line 43–56 and Line 58. Regenerate and commit pnpm-lock.yaml using pnpm 10.32.1.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 43 - 58, CI fails due to an outdated lockfile
after dependency/version changes; regenerate pnpm-lock.yaml using the declared
package manager version (packageManager value "[email protected]") by running pnpm
install with pnpm 10.32.1 locally or in CI, ensure the updated pnpm-lock.yaml is
added and committed alongside the package.json changes so the lockfile matches
the dependency versions listed (the dependencies block including
"@biomejs/biome", "@types/node", "typescript", "vitest", etc.).