What it means
pnpm has a safety setting called minimumReleaseAge. It refuses to install a package version until it has been public for a set time, so a freshly published bad release does not reach you at once. A package in your lock file is newer than that limit.
How to fix it
Wait. The package becomes allowed once it is old enough. Deploy again after the cutoff.
Or pin the previous version. Pin the package to the last release that is old enough, update the lock file, and commit it.
If you control the policy and accept the risk, you can relax minimumReleaseAge in your pnpm settings.