chore: remove root packageManager nonstandard field

[shivarm]

Description

Validation

Related Issues

closes: ##9004

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run pnpm format to ensure the code follows the style guide.
• I have run pnpm test to check if all tests are passing.
• I have run pnpm build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nodejs-org	Error		Jul 18, 2026 4:50am

[cursor]

PR Summary

Low Risk
Metadata and CI-only workflow changes; no runtime application or security-sensitive logic.

Overview
Removes the root packageManager field from package.json so the repo relies on devEngines.packageManager as the single source for the required pnpm version (closes #9004).

The PNPM updater workflow no longer derives the version from the deleted field; after pnpm self-update, it writes devEngines.packageManager.version using the live pnpm --version output via jq --arg.

^{Reviewed by Cursor Bugbot for commit cf5c0d2. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit e5abd86. Configure here.}

[avivkeller]

WARNING! Warning: Could not enable corepack because package.json is missing "packageManager" property

Looks like we needed that field

[ljharb]

only if you're using corepack - which you don't need to be.