Blogpnpm

ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION How to fix it.

pnpm refused packages in your lock file because they were published too recently. You can wait, pin the previous version, or relax the policy.

How the Agent API works
What you see
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] a package in your lockfile was
published too recently to be installed under the minimumReleaseAge policy
  • What it meansA package is too new for the policy
  • Fix oneWait until the cutoff passes
  • Fix twoPin the previous version
  • Fix threeRelax minimumReleaseAge

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.

01Questions

pnpm questions, answered.

Anything else? Write to us and a person answers.

support@antideploy.com
Is this a problem on Antideploy's side?

No. It is pnpm's own policy, set in your project or your pnpm settings.

Why did it appear today?

A dependency released a new version recently, and your lock file picked it up.

Does this failed deploy cost anything?

No. Failed deploys never count against your plan.

Deploy something. Start with one sentence.

Paste one sentence into your coding agent, click Approve once, and get a live link. No card, no trial clock.

Start from GitHub or a folder
Prompt copied Paste it into Claude Code, Codex or Cursor and press Enter.