Try disabling Metal builder.

Nop. Same problem.

Try deploying your project with a Dockerfile, see if that helps.

I can't atm, I would appreciate a fiix...

Hello panickz1;

can you share your package.json?

All was working now is not, in terms of deploying, I've not changed anything in package.json. As i told I have two instances with the same problem. One in NestJS the other is NextJS. This problem in not on our end, but I might stand corrected.

Redeploying the live commit fails..

got same problem here, still not fixed. happened in all node + pnpm services for me

I got problem too on couple services which use pnpm. Anyone fix that?

I have the same problem.

Same problem

This error means the build is trying to resolve pnpm from a bare major version ("9") and the resolver can't turn that into a concrete release. Corepack — which Railpack uses when it sees the packageManager field — requires an exact version, not a major. Fixes in order of likelihood:

In package.json, pin the exact version: "packageManager": "pnpm@9.15.9" (any full x.y.z you want — but it must be exact, pnpm@9 won't resolve). Delete any conflicting engines.pnpm entry while you're there.

If your pnpm version comes from engines.pnpm instead, change it from "9" to an exact "9.15.9" — the bare major hits the same resolution failure in the mise backend.

Alternatively add a mise.toml in the repo root with [tools] / pnpm = "9.15.9" — that overrides detection entirely.

If pinning doesn't fix it, it's the builder image's resolver cache (there have been broken mise/asdf backend states on builders — same family as the "Failed to resolve version 1.22.22 of yarn" threads). Since you already toggled Metal: a Dockerfile (FROM node:22-slim, RUN npm i -g pnpm@9.15.9, copy, install, build) bypasses Corepack/Railpack resolution completely and is the reliable escape hatch.

If option 1 fixes it, the root cause was the non-exact packageManager version — newer Railpack versions are stricter about it than older ones, which is why it "suddenly" broke.