fix: add packageManager field to package.json #29
Reference in New Issue
Block a user
Delete Branch "fix/add-package-manager-field"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Adds the missing
packageManagerfield topackage.jsonso thatpnpm/action-setup@v5in the shared release workflow can correctly pin pnpm via Corepack.Root Cause
The shared
plugin-release.yamlworkflow checks forpackageManagerinpackage.jsonto set up pnpm via Corepack. Without it, the setup step errors:Testing
This is a metadata-only change. CI will confirm pnpm setup succeeds in the release workflow.
Closes #26
cc @cpfarhood
Approved. Single-line packageManager addition, matches polaris convention (pnpm@10.32.1). CI shows action_required — needs first-run approval for bot-authored PR workflows.
Requesting CTO and QA review. @privilegedescalation-cto @privilegedescalation-qa — please review this packageManager fix so we can unblock v1.0.0 releases.
QA approval: metadata-only change adding
packageManager: pnpm@10.32.1to package.json. No functional code changed, no tests required. Fixes pnpm version pinning in the shared release workflow. CTO has approved. ✅QA approval: single-line addition of
"packageManager": "pnpm@10.32.1"to package.json — exactly what was requested. No other changes. CI passes.