chore: bump pnpm to 11.1.1#550
Merged
Merged
Conversation
…encies pnpm 11 removed the package.json `pnpm.ignoredBuiltDependencies` field and replaced it (along with onlyBuiltDependencies, neverBuiltDependencies, etc.) with `allowBuilds` in pnpm-workspace.yaml, requiring an explicit boolean per package whose lifecycle scripts need to run. - Migrate `ignoredBuiltDependencies: [isolated-vm]` to `allowBuilds.isolated-vm: false`. - Set every other package whose install scripts ran under pnpm 10 (esbuild, sharp, puppeteer, etc.) to `true` to preserve prior behavior. - Regenerate pnpm-lock.yaml under pnpm 11.1.1.
Contributor
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
@tanstack/ai
@tanstack/ai-anthropic
@tanstack/ai-client
@tanstack/ai-code-mode
@tanstack/ai-code-mode-skills
@tanstack/ai-devtools-core
@tanstack/ai-elevenlabs
@tanstack/ai-event-client
@tanstack/ai-fal
@tanstack/ai-gemini
@tanstack/ai-grok
@tanstack/ai-groq
@tanstack/ai-isolate-cloudflare
@tanstack/ai-isolate-node
@tanstack/ai-isolate-quickjs
@tanstack/ai-ollama
@tanstack/ai-openai
@tanstack/ai-openrouter
@tanstack/ai-preact
@tanstack/ai-react
@tanstack/ai-react-ui
@tanstack/ai-solid
@tanstack/ai-solid-ui
@tanstack/ai-svelte
@tanstack/ai-utils
@tanstack/ai-vue
@tanstack/ai-vue-ui
@tanstack/openai-base
@tanstack/preact-ai-devtools
@tanstack/react-ai-devtools
@tanstack/solid-ai-devtools
commit: |
Trimmed `allowBuilds` to the minimum set whose lifecycle scripts are required for `pnpm test:ci` to pass on a fresh checkout: - `esbuild`: kept true — Vite needs the platform binary - `protobufjs`: kept true — @google/genai (used by @tanstack/ai-gemini in CI) loads files generated by protobufjs's postinstall Everything else is `false`: - `sharp`, `workerd`: only reachable via `wrangler` (ai-isolate-cloudflare `dev:worker`/`deploy:worker` scripts — not in CI). - `puppeteer`: only used in examples/ts-code-mode-web (examples aren't built by Nx). - `@openrouter/sdk`: postinstall is `node scripts/check-types.js || true`, i.e. a no-op. - `@parcel/watcher`, `unrs-resolver`, `nx`: perf optimisations with working software fallbacks; skipping the postinstall loses cache/daemon speed, not correctness. - `isolated-vm`: already disabled (matches prior ignoredBuiltDependencies). Verified end-to-end: - Nuked node_modules, fresh `pnpm install` → no IGNORED_BUILDS warning. - `pnpm test:pr` (full CI gate: sherif/knip/docs/eslint/lib/types/build/build) → 169/169 tasks green.
Six commits behind on the pinned SHA; range is routine maintenance plus two action bumps relevant to this repo: - nrwl/nx-set-shas → v5 - pnpm/action-setup → v6 (handy now that we're on pnpm 11.1.1) Plus renovate config tweaks and dependency lockfile maintenance inside the upstream `TanStack/config` repo.
3 tasks
AlemTuzlak
added a commit
that referenced
this pull request
May 14, 2026
…pace.yaml (#558) pnpm v11 stopped reading settings from the \`pnpm\` field of \`package.json\` (https://github.com/pnpm/pnpm/releases/tag/v11.0.0). Settings have to live in \`pnpm-workspace.yaml\` instead. The repo's \`packageManager\` was bumped from pnpm v10 to v11.1.1 in #550, but the two settings under the \`pnpm\` key — \`overrides\` and \`patchedDependencies\` — weren't moved, so they've been silently ignored ever since. The \`abbrev\` override is benign, but the missing \`@changesets/assemble-release-plan\` patch is the cause of PR #554's broken bumps (anthropic 0.8.6 → 1.0.0 instead of → 0.9.0, gemini 0.10.3 → 1.0.0 instead of → 0.11.0, etc.). The patch short-circuits \`shouldBumpMajor\` for any \`peerDependencies\` change so peer-only bumps don't cascade into major bumps across the workspace. Verified locally with \`rm -rf node_modules && pnpm install\`: the patch is now applied (the early-return \`if (depType === 'peerDependencies')\` is present in \`node_modules/.pnpm/@changesets+assemble-releas_<hash>/node_modules/@changesets/assemble-release-plan/dist/changesets-assemble-release-plan.cjs.js\`). Once this lands, the changesets workflow on the next push to main will regenerate \`changeset-release/main\` with the correct minor bumps.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bump the pinned
packageManagerfrompnpm@10.17.0topnpm@11.1.1(latest patch on the 11.1 line). This is a major-version bump of pnpm; corepack/CI will pick up the new version automatically from thepackageManagerfield — no workflow changes needed.Test plan
pnpm installlocally regenerates the lockfile cleanly (lockfile format may change between major pnpm versions; if a lockfile update is needed it should land in this PR before merge).Notes