✖ Failed to resolve version 9 of pnpm
y-pakorn
PROOP

2 months ago

Build error on every pnpm + node services.

scheduling build on Metal builder "builder-ndvwhm"

fetching snapshot6 MB169ms

fetched snapshot sha256:2c60d6e37fa104eafea25e08d9761db6e7abbb692e37b7adecc1af1315e83345 (6.3 MB bytes)

unpacking archive17.6 MB173ms

using build driver railpack-v0.23.0

╭─────────────────╮

│ Railpack 0.23.0 │

╰─────────────────╯

↳ Found .dockerignore file, applying filters

↳ Detected Node

↳ Using pnpm package manager

Failed to resolve version 9 of pnpm

railpack process exited with an error

Solved

6 Replies

Status changed to Awaiting Railway Response Railway 2 months ago


tokendis
HOBBY

2 months ago

I've been having the same problem for the last hour. I did a redeploy with nixpacks instead of railpack and it worked again... So I blame railpack for now. I don't know what that does, but when I know everything is ok, I redeploy with nixpacks, then redeploy with railpack and it works. But not on this case, it only works with nixpacks for now.


scavestany
PRO

2 months ago

yep, same exact problem:

using build driver railpack-v0.23.0

╭─────────────────╮

│ Railpack 0.23.0 │

╰─────────────────╯

↳ Detected Node

↳ Using pnpm package manager

Failed to resolve version 9 of pnpm

railpack process exited with an error


Anonymous
PRO

2 months ago

Same here

╭─────────────────╮

│ Railpack 0.23.0 │

╰─────────────────╯

↳ Detected Node

↳ Using pnpm package manager

Failed to resolve version 9 of pnpm


2 months ago

Still experiencing this? It seems like a transient issue with GitHub packages.


Status changed to Awaiting User Response Railway 2 months ago


tokendis
HOBBY

2 months ago

All good now on my side, I switched to railpack again and it worked


Status changed to Awaiting Railway Response Railway 2 months ago


2 months ago

Cool. We're also not seeing any new reports of this. Resolving 🫡


Status changed to Awaiting User Response Railway 2 months ago


Status changed to Solved ray-chen 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...