Skip to content

v11 does not respect minimumReleaseAge setting in monorepo #11433

@maxdzin

Description

@maxdzin

Verify latest release

  • I verified that the issue exists in the latest pnpm release

pnpm version

11.0.3

Which area(s) of pnpm are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

No response

Reproduction steps

  1. At the monorepo handled by pnpm (starting from v11) in pnpm-workspace.yaml set minimumReleaseAge (or remove to use default value of 1440).
  2. Try to add the most recent version of some dependency.
  3. pnpm just install ignoring minimumReleaseAge setting no matter what set there (or used default).

Describe the Bug

In a monorepo starting from pnpm v11 minimumReleaseAge is ignore minimumReleaseAge setting or if it is not set, it ignores default value of minimumReleaseAge, so it is possible to install the latest version, no matter if its release time respects that setting or not. Tried as update and clean install.

Expected Behavior

pnpm must not allow to install dependencies those are not meet minimumReleaseAge interval specified (or its default value).

Which Node.js version are you using?

v24.15.0

Which operating systems have you used?

  • macOS
  • Windows
  • Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

Ubuntu

Metadata

Metadata

Assignees

Labels

Type

No fields configured for Bug.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions