Repository navigation
fix: patch Prisma configuration and build tooling dependencies - #198
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Production deployment dpl_ARPWuhNR5vhhYmCNneH5iK1XtxNX is READY and aliased to https://piccnewyork.org at cf42d43. Browser sign-in returned 200 with Google sign-in visible. Full local validation and fresh audit passed before merge; signed-in production flows remain limited by the authentication challenge in this browser session. No schema or production records changed. |
Problem and outcome
Patch the remaining configuration/build-tool advisories while retaining Prisma 6 and the existing application architecture.
Closes #197.
Validation
Clean npm ci, Prisma generation, config loader smoke check, and full npm run verify passed. Refreshed against main 5feada8: 56 test files / 248 tests, lint, types, Prisma validation and build. Fresh npm audit reports zero vulnerabilities. git diff --check passed.
Scope / risk
Four files: package.json, package-lock.json, SESSION.md, one existing test. Lockfile size is mainly esbuild platform-package relocation and Prisma tooling dependency changes; semantic versions reviewed. No schema migration, data write, access-control change, provider rewrite, or Prisma major upgrade. Scoped override must be revisited when Prisma upstream adopts the fixed dependency.
References: https://github.com/RebeccaStevens/deepmerge-ts/releases/tag/v8.0.0 and GHSA-ggr8-5vv4-36mx
Production verification will follow green CI and merge.