Skip to content

fix: portal/app build + Prisma Docker build failures#2149

Merged
Marfuen merged 3 commits into
mainfrom
tofik/fix-portal-and-prisma-build
Feb 17, 2026
Merged

fix: portal/app build + Prisma Docker build failures#2149
Marfuen merged 3 commits into
mainfrom
tofik/fix-portal-and-prisma-build

Conversation

@tofikwest
Copy link
Copy Markdown
Contributor

Summary

  • Portal & App: @comp/company exports compiled JS from dist/ but wasn't being built before next build. Added it to the prebuild step in both apps so Vercel deployments work.
  • API Dockerfile (Prisma panic): The prisma.config.ts with earlyAccess: true (multi-file schema) conflicts with --schema=dist/schema.prisma on the Linux Prisma engine, causing RuntimeError: panicked at relation.rs - index out of bounds. Fixed by temporarily bypassing the config during Docker build.
  • API Dockerfile (Prisma version): Updated production stage from prisma@6.13.0 to prisma@6.18.0 to match packages/db/package.json.

All three issues were introduced in PR #2128 (@comp/company package addition).

Test plan

  • Portal Vercel build succeeds (no more Module not found: @comp/company)
  • App Vercel build succeeds
  • API Docker build succeeds on CodeBuild (no more Prisma panic)
  • API starts and responds to health check

🤖 Generated with Claude Code

@vercel
Copy link
Copy Markdown

vercel Bot commented Feb 17, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
app Ready Ready Preview, Comment Feb 17, 2026 10:14pm
portal Ready Ready Preview, Comment Feb 17, 2026 10:14pm

Request Review

@cursor
Copy link
Copy Markdown

cursor Bot commented Feb 17, 2026

PR Summary

Medium Risk
Touches CI/build and Docker/Prisma generation steps; while not user-facing, misconfiguration can break deployments or runtime DB client generation across environments.

Overview
Ensures apps/portal and apps/app build reliably by running the @comp/company package build as part of their build lifecycle so next build can resolve the compiled dist/ exports during Vercel deployments.

Updates the API multi-stage Docker build to avoid Prisma engine failures when generating from a combined schema (temporarily bypassing the prisma.config.ts multi-file/early-access path during image build) and aligns the production-stage Prisma CLI version to 6.18.0 to match the workspace database package.

Written by Cursor Bugbot for commit 4b1a4ba. This will update automatically on new commits. Configure here.

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>
@tofikwest tofikwest force-pushed the tofik/fix-portal-and-prisma-build branch from cfc7111 to 8273ae5 Compare February 17, 2026 16:23
@vercel vercel Bot temporarily deployed to Preview – portal February 17, 2026 16:23 Inactive
@vercel vercel Bot temporarily deployed to Preview – app February 17, 2026 16:23 Inactive
@Marfuen Marfuen merged commit c478509 into main Feb 17, 2026
5 of 7 checks passed
@Marfuen Marfuen deleted the tofik/fix-portal-and-prisma-build branch February 17, 2026 22:12
claudfuen pushed a commit that referenced this pull request Feb 18, 2026
## [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))
@claudfuen
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 1.83.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants