feat: upgrade pnpm

[florian-lefebvre]

Changes

• Closes Repo can't be opened on GitHub codespaces #11130
• Upgrade pnpm to latest
• Allows renovate to update pnpm

Testing

Tests should still pass. Smoke tests are failing because docs pnpm version need to match (withastro/docs#8394)

Docs

N/A, no changeset

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2bd2cc4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[bluwy]

One of the big change with pnpm v9 is that it will validate packageManager matching your current running pnpm version before executing, and error if not matching. This means everyone working on this monorepo should be using corepack.

I'd probably like to hear thoughts on this if this affects anyone. Otherwise we can disable this restriction with https://pnpm.io/npmrc#engine-strict. I heard corepack can be tricky to use if you use pnpm to manage Node.js versions.

Also, we should update CONTRIBUTING.md about the latest pnpm version. There's a lot of logistics when upgrading pnpm hence why I disabled it in renovate 😅

[florian-lefebvre]

Should we recommend corepack in CONTRIBUTING.md?

[bluwy]

I'm ok with recommending corepack, and even requiring it if others are fine with it.

[bluwy]

I forgot about this. LGTM

[ematipico]

Let's 🐑 it