You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrade the repo's pnpm runtime from v10 to v11 in a single PR per the spec under `.specs/FR-2840-pnpm-v11-migration/`.
- package.json: bump engines.pnpm to ^11.0.0, drop the now-ignored pnpm field, add packageManager pnpm@11.0.8 (overrides moved to pnpm-workspace.yaml).
- pnpm-workspace.yaml: convert onlyBuiltDependencies (list) to allowBuilds (map), absorb overrides from package.json, drop minimumReleaseAgeExclude (its entries no longer matched the resolved tree under v11 and triggered metadata-time errors during resolution).
- .npmrc: drop engine-strict=true since engines.pnpm enforces this natively in v11; the file is documented as auth/registry-only per pnpm 11 scope.
- All 15 pnpm/action-setup invocations across workflows + the daily-test-improver composite action + agentic e2e-watchdog/e2e-healer .md/.lock.yml files now use version: 11.
- vitest.yml's lone pnpm/action-setup@v4 bumped to @v5 (cleanup observed during PR #7297 review).
- pnpm-lock.yaml regenerated under pnpm 11 via `pnpm install --merge-git-branch-lockfiles --no-frozen-lockfile`.
0 commit comments