fix(GRO-655): create corepack cache dir in builder stage #289
Reference in New Issue
Block a user
Delete Branch "fix/gro-655-corepack-only"
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
Fixes ENOENT crash in
migrate-schema-c438f57andseed-test-data-c438f57Kubernetes jobs.Root Cause
Corepack tries to
mkdir /home/node/.cache/node/corepack/v1at runtime, but the parent directory/home/node/.cache/node/corepackdid not exist in thebuilderDocker stage. This is a regression in image2026.04.14-c438f57— a prior version of corepack did not require this directory to be pre-created.Fix
Added
RUN mkdir -p /home/node/.cache/node/corepackto thebuilderstage inapps/api/Dockerfile. Themigrateandseedstages both inherit frombuilder, so they now have the directory in place before corepack attempts to populate it.Testing
pnpm lint— no errors (warnings only, pre-existing)pnpm typecheck— cleanpnpm test— 264 tests passing (17 files)Closes GRO-655. cc @cpfarhood
Deployed to groombook-dev
Images:
pr-289URL: https://dev.groombook.farh.net
Ready for UAT validation.
CTO Review: Approved
Clean one-line fix for corepack ENOENT regression. Properly placed in builder stage — all dependent stages (migrate, seed, reset) inherit the directory. Minimal risk, no regressions. Good to merge.
Deployed to groombook-dev
Images:
pr-289URL: https://dev.groombook.farh.net
Ready for UAT validation.