3 months ago
It looks like Railway just rolled out a change to upgrade Railpack to 0.15.2. That upgrade also seems to have upgraded Mise to the December release. Unfortunately, I'm now getting an error that it can't install Erlang 28.
✖ Failed to run mise command '/tmp/railpack/mise/mise-2025.12.12 latest erlang@28': exit status 1
mise ERROR command ["/tmp/railpack/mise/cache/erlang/kerl-4.4.0", "list", "releases", "all"] exited with code 1
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more informationI've installed Mise 2025.12.12 locally and was able to run mise latest erlang@28 with no problems, so I suspect it is some Railway specific issue. This is preventing any further deploys to my service, so I'd appreciate any help you can provide.
project id: 968fbf0e-c851-4e88-a772-1ece2d77f4be
service id: 874ab1b1-f4d1-460a-8cc8-ea426df9ee70
11 Replies
Update your mise.toml or .tool-versions to specify an exact version number instead of a fuzzy match like 28 or latest
3 months ago
Sorry about that Fugi! There was an issue yesterday where we had to rush out an update to Mise to fix python and node builds, but that inadvertently broke some elixir/erlang builds. I am to fix that today
3 months ago
I did also just release an update to Railpack that might fix it (0.15.3). That version will be released soon
@Fugi 👋 I help with railpack development. Could you share a bit more of your buildplan? What elixir version are you using?
3 months ago
the current railpack.json is
{
"$schema": "https://schema.railpack.com",
"provider": "elixir",
"packages": {
"elixir": "1.19-otp-28",
"erlang": "28",
"node": "22",
"pnpm": "7"
},
...
}but at the start of the issue it had "elixir": "1.18", instead. Neither worked.
@Fugi I looked into this and I'm not able to reproduce this. I think this is an intermittent error (which should be retried on the mise side; I'll look into that).
Could you give the build another attempt and see if it resolves?
3 months ago
Retried the build and it attempted with Railpack 0.15.3 this time, which has a new error. It does not look like a transient error?
3 months ago
Sorry for the delay, I've confirmed that the builds are working again. Thanks!
Status changed to Solved brody • 3 months ago