next.js

18164506 - CI: Another attempt to fix pnpm versions for next-stats-action on canary (#92550)

CI: Another attempt to fix pnpm versions for next-stats-action on canary (#92550) It looks like https://github.com/vercel/next.js/pull/92533 didn't fully solve our issue here: https://github.com/vercel/next.js/actions/runs/24162886733/job/70518191406#step:7:163 `corepack use pnpm@10.33.0` runs `pnpm install`, but we want to run `pnpm install` with specific flags including `--no-frozen-lockfile`. What I really want is some way to get corepack to update the `packageManager` field, but not run `pnpm install`. We already have to modify the `package.json` ourselves to fix `engines.pnpm`, so let's just not call `corepack use`. It seems that the changes to `packageManager` are picked up the next time that `pnpm` is run with no other interaction needed: