The eval update is blocked by a Bun 1.3.14 dependency-resolution bug, not a Core or autorouter test failure.
Eval requests the same schematic-solver archive directly and through another dependency. If the second request arrives after the archive has already been extracted, Bun incorrectly leaves it unresolved and reports “failed to resolve,” despite a successful download.
I reproduced this with identical packages and a clean cache: changing only the response order makes Bun 1.3.14 pass or fail. Bun 1.4.2 handles the failing order correctly and installs the unchanged eval manifest successfully. The bug is covered by [Bun’s upstream fix #35426.](https://github.com/oven-sh/bun/pull/35426)
The proposed fix is to pin eval’s test workflow to Bun 1.4.2 and run the full CI suite. Other eval jobs already use that version successfully. No Core, autorouter, or test-assertion changes are needed to address this install failure.
Abse
https://github.com/tscircuit/eval/pull/4907
Abse
codex investigated the issue
Seve
yep that's fine
Want to add to the conversation?
Reply in Discord so your notes stay connected to the source.