Fix pnpm-lock.yaml after E2E deletion on main #82

Merged
privilegedescalation-engineer[bot] merged 1 commits from hugh/fix-pnpm-lockfile-main into main 2026-05-11 20:11:55 +00:00
privilegedescalation-engineer[bot] commented 2026-05-11 17:46:59 +00:00 (Migrated from github.com)

Problem

Main branch CI is failing with ERR_PNPM_OUTDATED_LOCKFILE because @playwright/test was removed from package.json in commit 943d901 (E2E deletion PR #80 merge) but pnpm-lock.yaml was not regenerated.

Solution

Regenerate pnpm-lock.yaml by running pnpm install, which removes the stale @playwright/test entries.

Impact

  • Fixes CI failure on main branch
  • Unblocks further development
  • No functional changes - only lockfile synchronization

Related

Testing

CI will verify that pnpm install --frozen-lockfile succeeds.

## Problem Main branch CI is failing with `ERR_PNPM_OUTDATED_LOCKFILE` because `@playwright/test` was removed from `package.json` in commit 943d901 (E2E deletion PR #80 merge) but `pnpm-lock.yaml` was not regenerated. ## Solution Regenerate `pnpm-lock.yaml` by running `pnpm install`, which removes the stale `@playwright/test` entries. ## Impact - Fixes CI failure on main branch - Unblocks further development - No functional changes - only lockfile synchronization ## Related - This addresses the same root cause as [PRI-1153](https://paperclip.ing/PRI/issues/PRI-1153) (fixing lockfiles on E2E deletion PRs) - PR #80 that introduced the issue: https://github.com/privilegedescalation/headlamp-sealed-secrets-plugin/pull/80 ## Testing CI will verify that `pnpm install --frozen-lockfile` succeeds.
Sign in to join this conversation.