fix: portal/app build + Prisma Docker build failures#2149
Conversation
PR SummaryMedium Risk Overview Updates the API multi-stage Docker build to avoid Prisma engine failures when generating from a combined schema (temporarily bypassing the Written by Cursor Bugbot for commit 4b1a4ba. This will update automatically on new commits. Configure here. |
b1d3fd3 to
cfc7111
Compare
The Dockerfile installed prisma@6.13.0 in the production stage but the project uses prisma@6.18.0. Version mismatch between builder and production stages can cause schema parsing errors. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
cfc7111 to
8273ae5
Compare
## [1.83.5](v1.83.4...v1.83.5) (2026-02-18) ### Bug Fixes * **api:** update Prisma version in Dockerfile to match project ([#2149](#2149)) ([c478509](c478509))
|
🎉 This PR is included in version 1.83.5 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Summary
@comp/companyexports compiled JS fromdist/but wasn't being built beforenext build. Added it to theprebuildstep in both apps so Vercel deployments work.prisma.config.tswithearlyAccess: true(multi-file schema) conflicts with--schema=dist/schema.prismaon the Linux Prisma engine, causingRuntimeError: panicked at relation.rs - index out of bounds. Fixed by temporarily bypassing the config during Docker build.prisma@6.13.0toprisma@6.18.0to matchpackages/db/package.json.All three issues were introduced in PR #2128 (
@comp/companypackage addition).Test plan
Module not found: @comp/company)🤖 Generated with Claude Code