bug: v1.0.0 release workflow fails — missing packageManager field in package.json #26

Closed
opened 2026-03-24 22:10:50 +00:00 by privilegedescalation-qa[bot] · 1 comment
privilegedescalation-qa[bot] commented 2026-03-24 22:10:50 +00:00 (Migrated from github.com)

Bug Report

Summary

The v1.0.0 release workflow failed at the Setup pnpm step with:

Error: No pnpm version is specified.
Please specify it by one of the following ways:
  - in the GitHub Action config with the key "version"
  - in the package.json with the key "packageManager"

Root Cause

package.json is missing the packageManager field. The shared release workflow (plugin-release.yaml) uses pnpm/action-setup@v5, which requires either a version key in the action config or a packageManager field in package.json.

Fix

Add the packageManager field to package.json:

"packageManager": "pnpm@10.6.0"

Use the same pnpm version as specified in the lockfile (pnpm v9 lockfile format detected — check which pnpm version is installed in CI, e.g. pnpm@10.6.0 to match other plugins like polaris which uses pnpm@10.32.1).

Reproduction

  1. Merge the release/v1.0.0 branch to main (already done)
  2. Observe the Release workflow fails at Setup pnpm

Affected Repos

Same issue affects: headlamp-kube-vip-plugin, headlamp-tns-csi-plugin, headlamp-rook-plugin, headlamp-sealed-secrets-plugin

## Bug Report ### Summary The v1.0.0 release workflow failed at the `Setup pnpm` step with: ``` Error: No pnpm version is specified. Please specify it by one of the following ways: - in the GitHub Action config with the key "version" - in the package.json with the key "packageManager" ``` ### Root Cause `package.json` is missing the `packageManager` field. The shared release workflow (`plugin-release.yaml`) uses `pnpm/action-setup@v5`, which requires either a `version` key in the action config or a `packageManager` field in `package.json`. ### Fix Add the `packageManager` field to `package.json`: ```json "packageManager": "pnpm@10.6.0" ``` Use the same pnpm version as specified in the lockfile (pnpm v9 lockfile format detected — check which pnpm version is installed in CI, e.g. `pnpm@10.6.0` to match other plugins like polaris which uses `pnpm@10.32.1`). ### Reproduction 1. Merge the `release/v1.0.0` branch to `main` (already done) 2. Observe the Release workflow fails at `Setup pnpm` ### Affected Repos Same issue affects: headlamp-kube-vip-plugin, headlamp-tns-csi-plugin, headlamp-rook-plugin, headlamp-sealed-secrets-plugin
privilegedescalation-qa[bot] commented 2026-03-24 22:25:53 +00:00 (Migrated from github.com)

Status update: The per-repo fix PR was closed in favor of a systemic fix in privilegedescalation/.github#68, which adds version: latest to the shared plugin-release.yaml workflow. QA and CTO approval are in progress — once merged, the Release workflow will succeed and this issue can be closed.

**Status update:** The per-repo fix PR was closed in favor of a systemic fix in [privilegedescalation/.github#68](https://github.com/privilegedescalation/.github/pull/68), which adds `version: latest` to the shared `plugin-release.yaml` workflow. QA and CTO approval are in progress — once merged, the Release workflow will succeed and this issue can be closed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: privilegedescalation/headlamp-rook-plugin#26