chore: enforce pnpm 11

[KevinVandy]

🎯 Changes

✅ Checklist

• I have followed the steps in the Contributing guide.
• I have tested this code locally with pnpm test:pr.

🚀 Release Impact

• This change affects published code, and I have generated a changeset.
• This change is docs/CI/dev-only (no release).

Summary by CodeRabbit

• Chores
  • Updated package manager configuration to require pnpm version 11.0.0 or higher for development compatibility.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: db047937-3483-4a20-8a85-0fc92d9eeb03

📥 Commits

Reviewing files that changed from the base of the PR and between 6ddd247 and 8c8f7a6.

📒 Files selected for processing (1)

• package.json

---

📝 Walkthrough

Walkthrough

The root package.json is updated with an engines constraint that enforces pnpm version 11.0.0 or higher, complementing the existing packageManager field declaration.

Changes

pnpm version constraint

Layer / File(s)	Summary
pnpm version constraint package.json	An engines section specifying pnpm >=11.0.0 is added to enforce the minimum required version.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A pnpm version gleams so bright,
Eleven point oh, a shiny height,
Engines now enforce the way,
Modern tools for modern day! 📦✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description follows the template structure with all required sections present, but the 'Changes' section is completely empty with only a comment placeholder.	Fill in the 'Changes' section to describe what changes were made and why, e.g., 'Added pnpm >=11.0.0 engine constraint to package.json to ensure consistent tooling versions.'

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: enforce pnpm 11' clearly and concisely describes the main change: adding a version constraint for pnpm.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 8c8f7a6

Command	Status	Duration	Result
nx affected --targets=test:sherif,test:docs,tes...	✅ Succeeded	1s	View ↗
nx run-many --target=build	✅ Succeeded	<1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-05-21 21:28:33 UTC

[pkg-pr-new]

npm i https://pkg.pr.new/@tanstack/eslint-config@391

npm i https://pkg.pr.new/@tanstack/publish-config@391

npm i https://pkg.pr.new/@tanstack/typedoc-config@391

npm i https://pkg.pr.new/@tanstack/vite-config@391

commit: 8c8f7a6