Skip to content

file: dependencies are checked for minimumReleaseAge #12111

Description

@alumni

Verify latest release

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

pnpm version

11.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. Add a file: dependency that does not exist in the npm registry, e.g.:
{
  "dependencies": {
     "@types/my-cool-lib": "file:vendor/types__my-cool-lib-v1.0.0-final-final.tgz"
  }
}
  1. Run pnpm install.
  2. (optional) if the error didn't show up in step 2, run pnpm install again without node_modules but with the correct lockfile.

Describe the Bug

Error:

[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 2 lockfile entries failed verification:
  @types/my-cool-lib@1.0.0 could not be checked against minimumReleaseAge (GET https://repositories.my-registry.com/artifactory/api/npm/npm-virtual/@types%2Fmy-cool-lib: Forbidden - 403)

Expected Behavior

I would expect that local libraries are not checked in the registry.

Which Node.js version are you using?

24.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)

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Fields

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions