[GH-ISSUE #5617] [bug]: pnpm dlx prisma migrate deploy does not work anymore in old versions. #2173

New issue

Closed

opened 2026-03-16 23:28:08 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 23:28:08 +03:00

Owner

Originally created by @Breee on GitHub (Nov 25, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5617

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Platform

Web App

Browser

Chrome

Operating System

Linux

Bug Description

We have a hoppscotch instance running with hoppscotch/hoppscotch-backend:2025.5.4 (Yes its old, because we had some troubles updating it)
We usually execute pnpm dlx prisma migrate deploy in an init container (This is meant for updates and should not really do anything if the container is just restarted without bumping the version)
This command now fails:

Executing prisma migrations...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 59, reused 0, downloaded 50, added 0
Progress: resolved 90, reused 0, downloaded 88, added 0
Packages: +91
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 91, reused 0, downloaded 91, added 91, done
.../node_modules/prisma preinstall$ node scripts/preinstall-entry.js
.../node_modules/prisma preinstall: ┌────────────────────────────────────────────────────────────────────┐
.../node_modules/prisma preinstall: │    Prisma only supports Node.js versions 20.19+, 22.12+, 24.0+.    │
.../node_modules/prisma preinstall: │    Please upgrade your Node.js version.                            │
.../node_modules/prisma preinstall: └────────────────────────────────────────────────────────────────────┘
.../node_modules/prisma preinstall: Failed

How can a PINNED container image now suddenly require a higher node version?
How can we avoid this in the future?

Deployment Type

Self-hosted (on-prem deployment)

Version

2025.5.4

Originally created by @Breee on GitHub (Nov 25, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5617 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Web App ### Browser Chrome ### Operating System Linux ### Bug Description 1. We have a hoppscotch instance running with `hoppscotch/hoppscotch-backend:2025.5.4` (Yes its old, because we had some troubles updating it) 2. We usually execute `pnpm dlx prisma migrate deploy` in an init container (This is meant for updates and should not really do anything if the container is just restarted without bumping the version) 3. This command now fails: ``` Executing prisma migrations... Progress: resolved 1, reused 0, downloaded 0, added 0 Progress: resolved 59, reused 0, downloaded 50, added 0 Progress: resolved 90, reused 0, downloaded 88, added 0 Packages: +91 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 91, reused 0, downloaded 91, added 91, done .../node_modules/prisma preinstall$ node scripts/preinstall-entry.js .../node_modules/prisma preinstall: ┌────────────────────────────────────────────────────────────────────┐ .../node_modules/prisma preinstall: │ Prisma only supports Node.js versions 20.19+, 22.12+, 24.0+. │ .../node_modules/prisma preinstall: │ Please upgrade your Node.js version. │ .../node_modules/prisma preinstall: └────────────────────────────────────────────────────────────────────┘ .../node_modules/prisma preinstall: Failed ``` - How can a PINNED container image now suddenly require a higher node version? - How can we avoid this in the future? ### Deployment Type Self-hosted (on-prem deployment) ### Version 2025.5.4

kerem

2026-03-16 23:28:08 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 23:28:24 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Nov 25, 2025):

Hi, this appears related to #5600. Could you please try running pnpm exec prisma migrate deploy instead of pnpm dlx? The concern with using dlx is that it downloads the latest version of Prisma (v7), which requires a newer version of Node.js than what is currently available in your container.

@jamesgeorge007 commented on GitHub (Nov 25, 2025): Hi, this appears related to #5600. Could you please try running `pnpm exec prisma migrate deploy` instead of `pnpm dlx`? The concern with using `dlx` is that it downloads the latest version of Prisma (`v7`), which requires a newer version of Node.js than what is currently available in your container.

kerem commented

2026-03-16 23:28:29 +03:00

Author

Owner

@Breee commented on GitHub (Nov 25, 2025):

That seems to help, thanks

@Breee commented on GitHub (Nov 25, 2025): That seems to help, thanks