TanStack
OSS
ai
Sign in / Sign up
Open main menu
ai
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
fix-pnpm-v11-patches-workspace
5fd4ff29 fix(release): move pnpm overrides + patchedDependencies to pnpm-workspace.yaml 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.
by Alem Tuzlak
A
Succeeded
fix-pnpm-v11-patches-workspace
5fd4ff29 fix(release): move pnpm overrides + patchedDependencies to pnpm-workspace.yaml 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.
by Alem Tuzlak
A
Previous page
Previous
Next
Next page