Same issue here, builds are still failing

Can you please link to a specific build that has failed.

Sure, these are the logs from the latest failed build: https://railway.com/project/7089e588-1023-47ae-855e-81720df14929/logs?environmentId=1a126d2c-a7a6-48e8-84f2-5d8b946591dc&filter=%40snapshot%3Af16f34f8-c8ee-45fe-a28e-02eaca1baa94+OR+%40replica%3Af16f34f8-c8ee-45fe-a28e-02eaca1baa94&context=2025-08-01T14%3A11%3A03.438027157Z&start=1754057453891

Let me know if you need anything else or I should link in another format

Please link to a deployment instead of using the logs tab.

Maybe this is a better way of sharing? https://railway.com/project/7089e588-1023-47ae-855e-81720df14929/service/a136ef14-d375-4a82-86e1-a222414ff1d5?context=2025-08-01T14%3A11%3A03.438027157Z&environmentId=1a126d2c-a7a6-48e8-84f2-5d8b946591dc&id=6619a7d0-cabb-4bf9-bfc5-714d320080df&forceViewAll=true#build

In any case I think these are the relevant lines:

```
mkdir /etc/mise

Cached

create mise config

Cached

install mise packages: node, pipx, pipx:poetry, python

process "sh -c mise trust -a && mise install" did not complete successfully: exit code: 1

3s

mise node@22.18.0 install

mise python@3.12.11 install

mise node@22.18.0 download node-v22.18.0-linux-x64.tar.gz

mise python@3.12.11 download cpython-3.12.11+20250723-x86_64-unknown-linux-gnu-install_only_stripped.tar.gz

mise python@3.12.11 extract cpython-3.12.11+20250723-x86_64-unknown-linux-gnu-install_only_stripped.tar.gz

gpg: Signature made Thu Jul 31 21:47:23 2025 UTC gpg: using EDDSA key 5BE8A3F6C8A5C01D106C0AD820B1A390B168D356 gpg: Can't check signature: No public key

mise ERROR gpg failed gpg: Signature made Thu Jul 31 21:47:23 2025 UTC gpg: using EDDSA key 5BE8A3F6C8A5C01D106C0AD820B1A390B168D356 gpg: Can't check signature: No public key

mise python@3.12.11 python --version

mise python@3.12.11 Python 3.12.11

mise python@3.12.11 ✓ installed

mise ERROR failed to install core:node@22.18.0 mise ERROR gpg exited with non-zero status: exit code 2 mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

ERROR: failed to build: failed to solve: process "sh -c mise trust -a && mise install" did not complete successfully: exit code: 1
```

@brody Is there a way to force railpack to use a an older builder image? This would be a good workaround when something goes wrong with the latest update. I haven't found anything in the config and it seems to pull the latest version by default.

The issue isn't a new Railpack version or anything like that, the issue is upstream from Railpack.

Thank you. I have staged a variable change for you. Please apply it at your earliest convenience and let me know if that solves the build issue.

Thank you, this seem to be working I added it to another deployment, and it also worked there.

We have a production environment as well, will deploy that later today too, and if needed I'll add the ENV variable there as well if needed.

Is there anything else I should do?

Thank you for letting me know it has worked. If you run into the same issue on other services, you should indeed use the same variable.

But beyond that, no further action is needed on your part, since we will be looking into applying this patch automatically from within Railpack.

We've pushed a fix that should apply this patch automatically within Railway moving forward!

We've added a workaround in Railpack so this shouldn't happen again. I can explain a bit what this error is for context.

• On July 31, 2025 Node released version 22.18. This is the latest LTS version which Railpack uses by default

• Mise has a feature to verify the public key of the downloaded files. This key was missing for this new release and since it is the default that Railpack uses, many users were seeing builds fail with a Can't check signature: No public key error

• We quickly pushed and released a fix in Railpack to skip this check when using Node (https://github.com/railwayapp/railpack/pull/208). This fixed the problem for the majority of users

• A smaller subset of users use Node in with other languages (either with a custom Railpack config file, through env vars, or via another provider). In this case our fix was not being applied

• Today we released another fix to always skip the Node public key verification (https://github.com/railwayapp/railpack/pull/209). All Node builds should be good to go now

We still need to investigate the root cause and why the public key was missing, but the current fix was what Railway could do to workaround the upstream issue.