Let users choose whether pnpm provider updates respect the release-age delay

[Neonsy]

Could we add a provider update setting that lets users choose between updating immediately and respecting pnpm’s minimumReleaseAge policy?

PR #14295 proposes installing the exact version T3 Code advertises, fixing updates that leave the installed version unchanged. That also bypasses pnpm’s default release-age delay. Some users want the newest provider release immediately, while others prefer to keep that delay

The setting could offer two choices:

• Respect pnpm’s release-age policy: Only offer versions eligible under the effective pnpm policy, and explain when a newer release is waiting on the cooldown
• Update immediately: Request the advertised version using the pinned update command, with clear wording about bypassing the default cooldown

The advertised version, Update button, and copyable command should all follow the selected policy, so T3 Code offers the version it intends to install

I’d prefer respecting pnpm’s policy by default, with immediate updates available as an explicit choice. The first version could be limited to providers installed globally through pnpm

Related bug report: #14249

[Neonsy]

A real case for keeping the release-age policy as the default, and for guarding the "Update immediately" option

I updated Codex today with pnpm add -g @openai/codex@latest --config.minimum-release-age=0, which is what immediate updates amount to. @openai/codex@0.162.0 was published at 19:01 UTC, but its @openai/codex-win32-x64 platform package only appeared at 19:11, and its tarball still returned 404 at 19:15. pnpm 12.10.1 skipped it as a missing optional dependency and exited 0. Codex then failed on every launch:

Error: Missing optional dependency @openai/codex-win32-x64. Reinstall Codex: pnpm add -g @openai/codex@latest

So bypassing the cooldown can leave users with a broken CLI instead of just an older one, and pnpm's exit code doesn't reveal it. Rerunning the suggested reinstall fails the same way until the tarball is live

For the setting, that suggests:

• Update immediately: Warn that a fresh release may still be publishing, and after a zero exit run the provider's version check, so a failed launch is reported as a failed update and not "Provider updated"
• Respect the release-age policy: This avoids the problem entirely and is the safer default
• Shorter custom minimum time: Maybe setting it for the codex install to 1 hour in order to get the latest fast while reducing this exact problem

Environment: Windows 10, pnpm 12.10.1, Node 24.21.0, Codex 0.162.0