Rush 0.1.0-alpha.45 — Terminal, fixed
Two things had quietly broken on Apple Silicon: the built-in Terminal, and the updater itself. Both are fixed — and the release pipeline is hardened so neither can slip through again.
- The built-in Terminal opens a real shell again on Apple Silicon
- Auto-updates verify their signature and install instead of silently aborting
- The release build now fails closed if any binary links a non-system library
The Terminal works again on Apple Silicon
Rush ships a real terminal — a full login shell, right inside the app. On Apple
Silicon Macs it had started failing the instant you opened a tab, with a raw
posix_spawnp failed and no shell. The tiny helper Rush uses to launch your shell
was being built against libraries the signed, notarized app isn't allowed to load,
so the shell never got the chance to start.
It's now built strictly against the system toolchain. Open a tab and you get a real shell — run anything you'd run in any terminal, and drop into a coding agent like Claude Code right there inside Rush.
Updates that install themselves
Rush verifies a signature on every update before it installs one, so you only ever get a build we actually published. A mismatch between the manifest we signed and the one we served was making that check fail — which meant updates were quietly aborting instead of installing, and the fix for a bug could never reach the people hitting it.
The pipeline now serves exactly the manifest it signs. Updates verify and install on the next quit, with nothing for you to do. If you're reading this, the update that carried it already worked.
Built so it can't happen again
Both bugs came from the same root: a binary reaching for a library outside the system, which a notarized Mac app is not allowed to load. So the release build now checks every binary it ships and refuses to build if any of them link something outside the system libraries. The failure that broke the Terminal can't quietly ride along in a future build — the release stops itself first.
Platforms
