Skip to content

[comp] Production Deploy#2771

Merged
Marfuen merged 6 commits intoreleasefrom
main
May 6, 2026
Merged

[comp] Production Deploy#2771
Marfuen merged 6 commits intoreleasefrom
main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 6, 2026

This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.


Summary by cubic

Pin SSR functions to Vercel region iad1 for apps/app and apps/portal to co‑locate with our us‑east‑1 database and speed up SSR renders. Inline the AWS RDS CA bundle as RDS_CA_BUNDLE across apps and @trycompai/db to guarantee verified TLS under Turbopack, removing outputFileTracingIncludes and the need for NODE_EXTRA_CA_CERTS.

Written for commit 2694ece. Summary will update on new commits.

github-actions Bot and others added 5 commits May 6, 2026 16:18
Co-locates Next.js serverless functions with the us-east-1 database to
eliminate cross-Atlantic queries during render. SSR was previously
running in lhr1; every DB call inside a server component incurred ~90ms
RTT to us-east-1, compounding across the 5+ sequential queries on pages
like /[orgId]/overview.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-locates Next.js serverless functions with the us-east-1 database to
eliminate cross-Atlantic queries during render. Mirrors the change in
apps/app — the Vercel project default had drifted to lhr1, causing SSR
DB calls to cross the Atlantic on every render.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
perf(app): pin Vercel SSR functions to iad1
perf(portal): pin Vercel SSR functions to iad1
@vercel
Copy link
Copy Markdown

vercel Bot commented May 6, 2026

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

Project Deployment Actions Updated (UTC)
app (staging) Ready Ready Preview, Comment May 6, 2026 8:58pm
comp-framework-editor (staging) Ready Ready Preview, Comment May 6, 2026 8:58pm
portal (staging) Ready Ready Preview, Comment May 6, 2026 8:58pm

Request Review

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

…TracingIncludes

fix(db): inline RDS CA bundle to bypass Turbopack ignoring outputFileTracingIncludes
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 13 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/framework-editor/prisma/client.ts">

<violation number="1" location="apps/framework-editor/prisma/client.ts:4">
P3: Avoid editing generated prisma client artifacts directly. Apply this TLS change in the canonical source (packages/db/src/client.ts) and regenerate the app client so the change persists.

(Based on your team's feedback about treating apps/*/prisma client files as generated artifacts.) [FEEDBACK_USED]</violation>
</file>

Tip: cubic used a learning from your PR history. Let your coding agent read cubic learnings directly with the cubic MCP.
Fix all with cubic.

import { PrismaClient } from '@prisma/client';
import { PrismaPg } from '@prisma/adapter-pg';

import { RDS_CA_BUNDLE } from './rds-ca-bundle';
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot May 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: Avoid editing generated prisma client artifacts directly. Apply this TLS change in the canonical source (packages/db/src/client.ts) and regenerate the app client so the change persists.

(Based on your team's feedback about treating apps/*/prisma client files as generated artifacts.)

View Feedback

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/framework-editor/prisma/client.ts, line 4:

<comment>Avoid editing generated prisma client artifacts directly. Apply this TLS change in the canonical source (packages/db/src/client.ts) and regenerate the app client so the change persists.

(Based on your team's feedback about treating apps/*/prisma client files as generated artifacts.) </comment>

<file context>
@@ -1,6 +1,8 @@
 import { PrismaClient } from '@prisma/client';
 import { PrismaPg } from '@prisma/adapter-pg';
 
+import { RDS_CA_BUNDLE } from './rds-ca-bundle';
+
 const globalForPrisma = global as unknown as { prisma?: PrismaClient };
</file context>
Fix with Cubic

@Marfuen Marfuen merged commit 63e5b6a into release May 6, 2026
13 checks passed
@claudfuen
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 3.44.1 🎉

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants