Skip to content

allowedDeprecatedVersions undefined when configured in global config.yaml file #11429

@pro-sumer

Description

@pro-sumer

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. Create a global configuration file ~/.config/pnpm/config.yaml.
  2. Add an entry allowedDeprecatedVersions:
allowedDeprecatedVersions:
  "@humanwhocodes/config-array": "0.13.0"
  1. Run pnpm config get allowedDeprecatedVersions
  2. Result is undefined

Describe the Bug

Entry allowedDeprecatedVersions in global configuration file ~/.config/pnpm/config.yaml is ignored; same entry in project specific configuration file pnpm-workspace.yaml does work as expected.

Expected Behavior

Same result for both global and project specific configuration file:

{
  "@humanwhocodes/config-array": "0.13.0"
}

(instead of undefined)

Which Node.js version are you using?

v25.9.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

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions