5 months ago
Trying out Railpack on a Bun monorepo project. There is a .bun-version in the repo root, pinning the project to 1.2.17. This was correctly reflected by the version number displayed next to the Bun icon in the Deployments UI. However, during build, the Railpack header shows Bun 1.2.18 under the Packages section. The build runs to the install stage before failing with:
mise ERROR Tool not installed for shim: bun Missing tool version: core:bun@1.2.17
It seems like the pinned version isn't being propagated correctly to the beginning / mise install stage of the Railpack build.
I've worked around the issue for now by bumping the project to use bun 1.2.18, but I expect this will become an issue again when the next Bun patch release lands.
13 Replies
5 months ago
Hey Jensen,
Sorry for the late reply, happy you found a workaround for now I believe.
We just got in direct contact with the Bun team in our Slack to prevent this exact issue actually. You should see some movement from us here to better align with their release cadence. Thanks for reporting.
- Angelo
Status changed to Awaiting User Response Railway • 5 months ago
5 months ago
This issue has recurred for our frontend Railpack builds with the release of Bun v1.2.19.
Status changed to Awaiting Railway Response Railway • 5 months ago
5 months ago
Hello,
Railpack does not read the bun version from a .bun-version file, but you can set the version with a RAILPACK_BUN_VERSION service variable.
let me know if that works for you.
Best,
Brody
Status changed to Awaiting User Response Railway • 5 months ago
5 months ago
Setting RAILPACK_BUN_VERSION does work, but it's still not clear to me why I need to do so. If .bun-version is ignored, then I would expect railpack and mise to default to the latest Bun release. This does appear to be the case in the build plan log:bun │ 1.2.19 │ railpack default (latest)
but the build still fails withmise ERROR Tool not installed for shim: bunMissing tool version: core:bun@1.2.18
(until I set RAILPACK_BUN_VERSION=1.2.18).
In other words, now that you have corrected my assumption about `.bun-version`, I don't know what in my project is causing mise to see a dependency on 1.2.18.
Status changed to Awaiting Railway Response Railway • 5 months ago
4 months ago
Heya, this is because railpack does not detect the 1.2.18 version and does not pass it to mise. mise then tries to use a version it was not given, causing the error.
Status changed to Awaiting User Response Railway • 5 months ago
4 months ago
Making sure I understand this correctly - you're saying misedoes respect .bun-version, but railpack doesn't, so I need to ensure .bun-version and RAILPACK_BUN_VERSION always match?
Status changed to Awaiting Railway Response Railway • 5 months ago
4 months ago
That's correct - I'll ticket this for our product team as railpack should ideally detect your version from the .bun-version file 
Status changed to Awaiting User Response Railway • 5 months ago
4 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
4 months ago
🛠️ The ticket Version file inconsistency issue has been marked as backlog.
4 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 4 months ago
3 months ago
🛠️ The ticket Version file inconsistency issue has been marked as todo.
3 months ago
🛠️ The ticket Version file inconsistency issue has been marked as in progress.
3 months ago
We've added support for this here, https://github.com/railwayapp/railpack/pull/258. It will be live soon!
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
✅ The ticket Version file inconsistency issue has been marked as completed.
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 2 months ago