fix(GRO-631): pin pnpm version and guard against duplicate CD PRs #284
Reference in New Issue
Block a user
Delete Branch "feature/gro-631-ci-pnpm-pin"
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
pnpm/action-setup@v4toversion: '9.15.4'in all 5 CI jobs (lint-typecheck, test, e2e, build, web-e2e) to match the monorepo'spackageManagerfield and prevent lockfile driftgroombook/infrabefore callinggh pr create, merging it instead if foundkubectl delete job migrate-schemacommand (main-branch migrations now use SHA-suffixed names)Closes GRO-649. Parent: GRO-631.
cc @cpfarhood
Verified all acceptance criteria:\n\n- [x] All 5 steps specify \n- [x] CD job checks for existing open PR before calling \n- [x] Line 241 stale is removed\n- [x] CI workflow YAML is valid (lint/typecheck passed)\n- [x] PR title: \n\nCI Status: Lint ✅, Typecheck ✅, Test ✅, E2E Tests ✅, Build ✅
Verified all acceptance criteria: All 5 pnpm/action-setup@v4 steps specify version 9.15.4. CD job checks for existing open PR before calling gh pr create. Line 241 stale kubectl delete job migrate-schema is removed. CI workflow YAML is valid (lint/typecheck passed). CI Status: Lint, Typecheck, Test, E2E Tests, Build all passed.
Deployed to groombook-dev
Images:
pr-284URL: https://dev.groombook.farh.net
Ready for UAT validation.
CTO Review: Approved
CI workflow changes (GRO-649):
packageManager: pnpm@9.15.4|| trueongh pr listprevents failurekubectl delete job migrate-schemaremoval correctDocker changes (GRO-631):
Minor follow-up: Web Dockerfile HEALTHCHECK uses
curlbutnginx:alpinedoesn't include it — needsRUN apk add --no-cache curlor switch towget. Low severity since K8s probes handle health checking.Merging after branch update. cc @cpfarhood
Deployed to groombook-dev
Images:
pr-284URL: https://dev.groombook.farh.net
Ready for UAT validation.