fix(infra): Prisma engine crashes due to OpenSSL version mismatch

[eliteprox]

Summary

Removes the "native" binary target from the Prisma schema to prevent engine crashes caused by OpenSSL version mismatches on Node 22+ / OpenSSL 3.5+ environments. Pins the project to Node 20 LTS via .nvmrc to lock dev environments to a known-stable OpenSSL 3.0.x combination.

Changes

• Removed "native" from binaryTargets in packages/database/prisma/schema.prisma — all required deployment targets are already explicitly listed (darwin-arm64, linux-arm64-openssl-3.0.x, debian-openssl-3.0.x, rhel-openssl-3.0.x, linux-musl-openssl-3.0.x), making "native" redundant and a source of mismatches
• Added .nvmrc pinning Node 20 LTS to prevent accidental local regressions on Node 22+

Type

• Feature
• Bug fix
• Refactor
• Documentation
• CI / Tooling
• Plugin (new or update)
• Dependencies

Plugin(s) Affected

Checklist

• Tests pass locally
• Lint passes (npm run lint)
• Build succeeds (npm run build)
• No new lint warnings introduced
• Breaking changes documented below
• Database migration included (if Prisma schema changed)

Breaking Changes

None — removing "native" does not affect any deployment target. All production platforms are covered by the explicit targets that remain.

Screenshots / Recordings

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
naap-platform	Ready	Preview, Comment	Mar 10, 2026 4:54pm

[github-actions]

🗃️ Database Migration Detected

This PR includes changes to Prisma schema files. Please ensure:

• Migration is backward-compatible or a rollback plan exists
• Data migration scripts are included if needed
• Schema changes will be auto-applied to the preview database (Neon preview branch) during the Vercel preview deployment
• Verify the preview deployment works correctly with the new schema
• On merge to main, schema changes will auto-promote to production via prisma db push

Preview DB: This PR's Vercel preview deployment uses an isolated Neon database branch. Schema changes are applied automatically via prisma db push during the preview build. The preview branch is reset after each production deploy.

Requesting review from the core team: @livepeer/core

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates Node.js version requirement to 20, simplifies RequireAuth component by removing unused auth context values from dependency tracking, and adjusts Prisma generator configuration to prevent OpenSSL compatibility issues.

Changes

Cohort / File(s)	Summary
Node.js Configuration .nvmrc	Specifies Node.js version 20 as the project runtime requirement.
Auth Context Refactoring apps/web-next/src/contexts/auth-context.tsx	Removes unused user and authErrorStatus values from RequireAuth component destructuring and dependency array, keeping only isAuthenticated, isLoading, and hasAnyRole.
Prisma Generator Configuration packages/database/prisma/schema.prisma	Removes "native" from binaryTargets to prevent OpenSSL version mismatch issues on Node 22+/OpenSSL 3.5+; adds clarifying comment above the target list.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• #194: Modifies the same RequireAuth logic in auth-context.tsx, adjusting which auth values are used and effect dependencies.

Suggested labels

scope/shell, size/S

Suggested reviewers

• seanhanca

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main infrastructure fix addressing Prisma engine crashes from OpenSSL version mismatches, which is reflected in the Prisma schema changes and .nvmrc file addition.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/openssl

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

⏳ Review reminder — This PR has been waiting for review for over 24 hours.

@team — this PR needs a review.

[github-actions]

🚨 Review SLA exceeded (72 h) — This PR has been waiting for review for over 72 hours. Please prioritize.

@team — urgent review needed.