# ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION How to fix it.

URL: https://antideploy.com/blog/pnpm-minimum-release-age-violation

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

**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
```

## At a glance

- **What it means**: A package is too new for the policy
- **Fix one**: Wait until the cutoff passes
- **Fix two**: Pin the previous version
- **Fix three**: Relax minimumReleaseAge

Published 7 October 2026. Facts checked 7 October 2026. 1 min read.

## 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.

## pnpm questions, answered.

Anything else? Write to us and a person answers.

[support@antideploy.com](mailto: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.

## More guides, and the platform.

Each platform page covers one part of Antideploy: what it does, where it stops and the questions people ask. [See the whole platform](https://antideploy.com/platform), or [all the guides](https://antideploy.com/blog).

- [ERR_PNPM_IGNORED_BUILDS Ignored build scripts](https://antideploy.com/blog/pnpm-ignored-build-scripts): pnpm blocked install scripts for packages like esbuild and sharp. Allow them in pnpm-workspace.yaml.
- [npm ci can only install packages when your package.json and package-lock.json are in sync](https://antideploy.com/blog/npm-ci-can-only-install-packages-when-package-json-and-package-lock-json-are-in-sync): The lock file does not match package.json. Run npm install and commit the lock file.
- [npm error notarget No matching version found](https://antideploy.com/blog/npm-error-no-matching-version-found): No published version matches the range in package.json. Check the version and the spelling.

- [Deployments](https://antideploy.com/platform/deployments)
- [Logs and monitoring](https://antideploy.com/platform/logs-and-monitoring)

Facts on this page were checked against the live platform on 7 October 2026.

## 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.

To set this up, give your coding agent this sentence:

```text
Set this project up to deploy on Antideploy. Fetch https://antideploy.com/agent.md and follow it.
```