7 Commits

Include renames

Author	SHA1	Message	Date
Marc-André Bombeck	4f2af7c544	test(release): hold the image's Prisma CLI install to the app's versions ... The guard pinned the npm-installed dotenv in the Dockerfile to a literal, which is how that install came to trail the app tree by a patch without anything noticing. It now reads the Prisma and dotenv versions from package.json and asks the Dockerfile for the same ones, engines included.	2026-10-22 07:06:51 +02:00
Marc-André Bombeck	369775e039	chore(deps): move dotenv to 18 ... The breaking changes in 18 do not reach this repository: nothing preloads dotenv with -r, nothing reads a .env.vault, and both entry points in use (the default export in prisma.config.ts and the side-effect dotenv/config import in the one-shot scripts) keep their behaviour. dotenv/config stays quiet by default. What does change is the load message, which now goes to stderr. Prisma reads prisma.config.ts on every migrate deploy at container start, so both loads there pass quiet: true rather than adding two stderr lines to each boot. The image's /opt/prisma-cli install, which the config resolves dotenv from, moves to the same 18.0.6.	2026-10-10 01:08:57 +02:00
Marc-André Bombeck	403eabb888	fix: restore runtime Prisma migration loading (#574)	2026-07-21 06:36:13 +02:00
Marc-André Bombeck	085aa3f5c5	fix: harden pnpm supply chain and runtime image (#572)	2026-07-21 04:36:53 +02:00
Marc-André Bombeck	5fe952b63d	fix(ci): harden release and e2e verification	2026-07-21 02:30:40 +02:00
Marc-André Bombeck	b38f41b99d	chore(release): prepare v1.31.4	2026-07-21 01:34:29 +02:00
Marc-André Bombeck	914e7658db	ci: harden image publishing	2026-07-20 23:47:19 +02:00