Skip to main content

RFC โ€” Upgrade pnpm 9.15.3 โ†’ 10/11 (qontak-customer-fe)

Bucket item: A12 ยท Class: ๐ŸŸก Standard ยท Jira Story: pending mint (Task: TF-3556) ยท Epic: TF-3500

Source: Qontak_Stack_Analysis_Repository_Detail_July_2026, qontak-customer-fe tab, row 8.

Context / Problemโ€‹

qontak-customer-fe currently pins pnpm 9.15.3 via corepack prepare (Dockerfile:9). pnpm 9's support status is Approaching end of support; the current major is pnpm 11.x.

Proposed changeโ€‹

Upgrade the pinned pnpm version to 10.x or 11.x during a maintenance window. pnpm 11 requires Node โ‰ฅ22, already satisfied by the production build image (node:22-alpine).

Execution plan (call to action)โ€‹

  1. Bump the corepack prepare pin in Dockerfile:9 to the target pnpm version (10.x or 11.x).
  2. Regenerate/verify the lockfile format against the new pnpm major; resolve any format warnings.
  3. Run pnpm install, pnpm build, pnpm test locally and in CI against the bumped version.
  4. Land during a maintenance window to isolate any CI breakage from unrelated feature changes.

Risks & rollbackโ€‹

  • Risk: low-medium โ€” lockfile format changes between pnpm majors can produce large diffs or resolution differences; CI must be green before merge.
  • Rollback: revert the Dockerfile pin + any lockfile regeneration commit.

Open questionsโ€‹

  1. pnpm 10 or straight to 11? (11 is current major; 10 is a smaller step if 11 has surprises.)
  2. Any CI runner image pinned to an older Node that would need bumping alongside this?