3 months ago
Hey, my apps suddenly started throwing this error during build, is there something happening with railway infra?
Failed to resolve version 24.12.0 of node
Metal build
Thanks
15 Replies
3 months ago
yes, I also have an issue during build:
{ "message": "install mise packages: caddy", ... }
do you have this message as well?
smcepeda
yes, I also have an issue during build:{ "message": "install mise packages: caddy", ... }do you have this message as well?
3 months ago
no, i dont, i see only those:
using build driver railpack-v0.15.1
╭─────────────────╮
│ Railpack 0.15.1 │
╰─────────────────╯
↳ Detected Node
↳ Using npm package manager
Failed to resolve version 24.12.0 of node
nodejs set the latest LTS few days ago - 10th dec
tried changing the node versions in package.json and nixpacks, but didnt help me
3 months ago
I'm also getting this issue. Builds about 30 minutes ago worked fine, with no new changed introduced.
Railpack + Metal build.
It affects all my services and environments both on node 24 and node 22.
jannisbecker
I'm also getting this issue. Builds about 30 minutes ago worked fine, with no new changed introduced.Railpack + Metal build.It affects all my services and environments both on node 24 and node 22.
3 months ago
Yes exactly, i got the first issue approx 50mins ago, no environmental changes made in my projects too.
3 months ago
Looks like some issues with Railpack, deployments until yesterday went fine, all that are done today are failed
3 months ago
same problem
3 months ago
Same error, I tried specifying exact versions of node and the error persists, without any changes to the code.
3 months ago
Same on node 22
3 months ago
upvote the original post, so the team sees it asap
3 months ago
also seeing it on node version 22, and i'm using bun
3 months ago
same
3 months ago
working now
3 months ago
managed to deploy, all good
3 months ago
failing on image build.
3 months ago
Railpack uses a tool called Mise to add various packages into your container images and the service that provided the up-to-date versions of those packages went down for a bit today. It should be resolved now, try redeploying your service.
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Solved echohack • 3 months ago
