Skip to content

manage-package-manager-versions flag not propagating to workspaces #8667

@y-nk

Description

@y-nk

Verify latest release

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

pnpm version

9.11

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

Package manager compatibility

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

No response

Reproduction steps

  1. Create a pnpm workspace with 2 workspaces.
  2. Have manage-package-manager-versions=true in .npmrc at root level
  3. Have packageManager="pnpm@9.1.0" in root level's package.json
  4. pnpm --version → 9.1.0
  5. cd workspaceA
  6. pnpm --version → not 9.1.0

Describe the Bug

the pnpm version of a workspace is not matching the one defined in the root level of the monorepo

Expected Behavior

pnpm version should remain the same as the monorepo root one unless explicitly redefined in each workspace.

Additional Notes

if it's not a bug, it could be a feature flag such as workspace-inherit-package-manager-version 🙏

Which Node.js version are you using?

20.18

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)

github action-runner (ubuntu)

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions