chore: enforce pnpm 11

[Sheraff]

Adds engines.pnpm >=11.0.0 to TanStack/intent.

Scenario	Result
pnpm@11+ install	Allowed
pnpm@11+ run ...	Allowed
pnpm@9 install	Blocked by engines.pnpm
pnpm@9 run ...	Blocked by engines.pnpm
pnpm@10 install with default pnpm version management	Usually hands off to packageManager and runs as the declared pnpm version
pnpm@10 run ... with default pnpm version management	Usually hands off to packageManager and runs as the declared pnpm version
pnpm@10 install with version handoff disabled	Blocked by engines.pnpm
pnpm@10 run ... with version handoff disabled	Blocked by engines.pnpm
pnpm@9/10 list	Not blocked
pnpm@9/10 exec ...	Not blocked

Field	What It Does
packageManager	Helps tools/newer pnpm select or hand off to the declared pnpm version
engines.pnpm: ">=11.0.0"	Fails important project workflows when an older pnpm is actually executing them
engines.pnpm	Does not intercept every pnpm subcommand

Summary by CodeRabbit

• Chores
  • Updated minimum pnpm version requirement to 11.0.0.

[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: 41fa5662-8947-44f8-b14c-77b4ae44acd8

📥 Commits

Reviewing files that changed from the base of the PR and between 8c64c66 and e749320.

📒 Files selected for processing (1)

• package.json

---

📝 Walkthrough

Walkthrough

This PR adds a pnpm version constraint to package.json, requiring pnpm version 11.0.0 or higher via the engines field. No dependencies, scripts, or other package metadata are modified.

Changes

pnpm Version Constraint

Layer / File(s)	Summary
pnpm version requirement package.json	The engines field is added with a pnpm version constraint of >=11.0.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A tiny hop in package land,
Where pnpm's version must now stand—
Eleven or greater, the constraint declares,
One little change shows how the project cares! 📦✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete; it lacks the required template sections including the 'Changes' section, the 'Checklist' items, and the 'Release Impact' section.	Add the required template sections: a 'Changes' section describing the motivation, checklist items confirming testing and contribution guide compliance, and 'Release Impact' indicating whether a changeset is needed.

✅ 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 pnpm version constraint to enforce pnpm 11+.
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

---

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

[nx-cloud]

View your CI Pipeline Execution ↗ for commit e749320

Command	Status	Duration	Result
nx run-many --targets=build --exclude=examples/**	✅ Succeeded	<1s	View ↗

---

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

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@tanstack/intent@139

commit: e749320