Bail if lockfile version is newer than pnpm version can handle?

[ts-playerdata]

We've seen a few instances lately of developers encountering issues after upgrading our supported pnpm version to v9, who are still running pnpm@8.

The repo now contains a lockfile which was generated with pnpm@9. Seemingly, if a developer has pnpm@8, and runs pnpm i in their repo, the installation is allowed to continue, wreaking havoc since:

a) the lockfile is regenerated (with an older lockfile version), leading to
b) dependency resolution issues which are difficult to pin down and diagnose

Apologies if this has been discussed before (I feel sure it must have been, but can't find a relevant discussion), but is there a case for aborting installation if a version of pnpm is used to install with an incompatible lockfile version? For example, a lockfile is present using lockfileVersion: '9.0', and pnpm@8 is used to install - should this abort?

Adopting such a strategy would have prevented a lot of head scratching these past few weeks.