fix(api): add debian-openssl-3.0.x to Prisma binaryTargets #529

Merged
jason.woltje merged 1 commits from fix/prisma-openssl-target into main 2026-02-27 02:44:12 +00:00
Owner

API crashes on deploy: Prisma client generated for debian-openssl-1.1.x but node:24-slim container needs debian-openssl-3.0.x. Adds explicit binaryTargets to schema.prisma. Also cleans inline comments from .env.example rate limit values that Portainer treats as part of the value.

API crashes on deploy: Prisma client generated for debian-openssl-1.1.x but node:24-slim container needs debian-openssl-3.0.x. Adds explicit binaryTargets to schema.prisma. Also cleans inline comments from .env.example rate limit values that Portainer treats as part of the value.
jason.woltje added 1 commit 2026-02-27 02:44:05 +00:00
fix(api): add debian-openssl-3.0.x to Prisma binaryTargets
All checks were successful
ci/woodpecker/push/api Pipeline was successful
d49a978252
Prisma client was generated for debian-openssl-1.1.x but the
node:24-slim Docker image runs Debian Bookworm with OpenSSL 3.0.x.
Adding explicit binaryTargets ensures the correct query engine is
always generated regardless of build host.

Also removes inline comments from .env.example rate limit values —
Portainer treats trailing comments as part of the value.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
jason.woltje merged commit 83d5aee53a into main 2026-02-27 02:44:12 +00:00
jason.woltje deleted branch fix/prisma-openssl-target 2026-02-27 02:44:12 +00:00
Sign in to join this conversation.