🐛 New version not picked up

[Netail]

VS Code version

1.113.0

Extension version

3.5.0

Biome version

2.4.9

Operating system

• Windows
• macOS
• Linux

Description

When bumping biome in a pnpm monorepo from 2.3.11 to 2.4.9, it seemed that the vscode extension did not pick up the new version yet. Tried restarting the Biome LSP through the vscode command pallet, but ended up having to restart my IDE

Steps to reproduce

1. Have 2.3.11 installed
2. Bump to 2.4.9 in package.json & run pnpm install
3. Bottom biome icon still displays 2.3.11 & linting errors with 2.4.9 not displaying in files

Expected behavior

Biome extension using newly installed version

Does this issue occur when using the CLI directly?

Not sure / Not applicable

Link to a minimal reproduction

No response

Logs

2026-03-27 15:17:34.261 [info]  🔒 Started listening for lockfile changes.
2026-03-27 15:17:34.261 [info]  ⚙️ Started listening for extension settings changes.
2026-03-27 15:17:34.261 [info]  ✅ Biome is ready.
2026-03-27 15:20:35.327 [info]  🔒 Lockfile ".../my-repo/pnpm-lock.yaml" changed.
2026-03-27 15:20:35.327 [info]  🔄 Restarting Biome...
2026-03-27 15:20:36.333 [info]  🔒 Started listening for lockfile changes.
2026-03-27 15:20:36.333 [info]  ⚙️ Started listening for extension settings changes.
2026-03-27 15:20:36.388 [info]  ✅ Biome is ready.

[nhedger]

Did you redact the path to the lock file or is that the real path ?

[Netail]

Did you redact the path to the lock file or is that the real path ?

I redacted the path, it included some sensitive data

[nhedger]

Thanks, I was able to reproduce. Looks like a regression was introduced in v3.5.0. I'll take a look

[nhedger]

Actually, it may be a pnpm issue. I can't seem to reproduce when using Bun.

[nhedger]

Reverted the fix because of #1005