🔧 Update Prisma schema to include additional binary target

[sasamuku]

Added runtime to avoid the following error on trigger.dev:

Invalid `prisma.repository.findUnique()` invocation: Prisma Client could not locate the Query Engine for runtime "debian-openssl-3.0.x". This happened because Prisma Client was generated for "darwin-arm64", but the actual deployment required "debian-openssl-3.0.x". Add "debian-openssl-3.0.x" to `binaryTargets` in the "schema.prisma" file and run `prisma generate` after saving it: generator client { provider = "prisma-client-js" binaryTargets = ["native", "rhel-openssl-3.0.x", "debian-openssl-3.0.x"] } The following locations have been searched: /node_modules/.pnpm/@[email protected][email protected][email protected][email protected]/node_modules/.prisma/client / /Users/hoshino/.local/share/go/src/github.com/liam-hq/liam/node_modules/.pnpm/@[email protected][email protected][email protected][email protected]/node_modules/@prisma/client /.prisma/client /tmp/prisma-engines

Issue

• resolve:

Why is this change needed?

What would you like reviewers to focus on?

Testing Verification

What was done

🤖 Generated by PR Agent at 646c0ef

• Added debian-openssl-3.0.x to Prisma binaryTargets.
• Updated Prisma schema to support Trigger.dev runtime.

Detailed Changes

	Relevant files
Enhancement	schema.prisma Add Debian OpenSSL 3.0.x to Prisma binary targets                frontend/packages/db/prisma/schema.prisma Added debian-openssl-3.0.x to binaryTargets. Updated Prisma generator configuration for compatibility. +1/-1

Additional Notes

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 646c0ef

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
liam-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 14, 2025 9:49am
liam-erd-sample	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 14, 2025 9:49am

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
test-liam-docs	⬜️ Ignored (Inspect)			Mar 14, 2025 9:49am
test-liam-erd-sample	⬜️ Ignored (Inspect)			Mar 14, 2025 9:49am
test-liam-erd-web	⬜️ Ignored (Inspect)			Mar 14, 2025 9:49am

[supabase]

Updates to Preview Branch (add_binary_target_for_trigger_dev) ↗︎

Deployments	Status	Updated
Database	✅	Fri, 14 Mar 2025 09:42:28 UTC
Services	✅	Fri, 14 Mar 2025 09:42:28 UTC
APIs	✅	Fri, 14 Mar 2025 09:42:28 UTC

Tasks are run on every commit but only new migration files are pushed.
Close and reopen this PR if you want to apply changes from existing seed or migration files.

Tasks	Status	Updated
Configurations	✅	Fri, 14 Mar 2025 09:42:34 UTC
Migrations	✅	Fri, 14 Mar 2025 09:42:36 UTC
Seeding	✅	Fri, 14 Mar 2025 09:42:36 UTC
Edge Functions	✅	Fri, 14 Mar 2025 09:42:36 UTC

---

View logs for this Workflow Run ↗︎.
Learn more about Supabase for Git ↗︎.

[qodo-merge-pro-for-open-source]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[qodo-merge-pro-for-open-source]

PR Code Suggestions ✨

No code suggestions found for the PR.

[hoshinotsuyoshi]

LGTM! thank you!