On aarch64 the packaged Hermes app was seeded into apps/desktop/release/linux-unpacked, the directory electron-builder uses on x86_64. On ARM it builds into linux-arm64-unpacked. So the first hermes update put the rebuilt app beside the seeded one instead of replacing it. The menu launcher then kept opening the old app, and the stale copy stayed on disk.
- Seed location:
omarchy-install-hermes-clinow seeds intolinux-arm64-unpackedwhenomarchy-hw-aarch64, so an update swaps the app in place. Its staging directory follows the name. - Existing ARM installs: ones seeded under
linux-unpackedsince aarch64hermes-desktopshipped (omacom/omarchy-pkgs#373, 2026-10-21) keep that copy.--checkstill passes for them, and--nowdoesn't seed a second app. - Tests:
hermes-desktop-install-test.shmocksomarchy-hw-aarch64, so its scenarios stay x86_64 whatever the host. It adds an ARM fresh install and an ARM install seeded under the old name. Both fail against the old installer.
The launcher half is omacom/omarchy-pkgs#1393: it opens the newest app in either directory, which covers machines already seeded under the old name.
Verified on an N1x (aarch64) with a scratch home and the real hermes-desktop package. A fresh omarchy-install-hermes-cli --now seeded linux-arm64-unpacked, which Hermes' own lookup resolves, and the app launched from there. hermes-desktop-install-test.sh, hermes-cli-test.sh, hermes-mise-migration-test.sh and ./test/cli pass.
🤖 Generated by Opus 5.5 in Claude Code.
[Medium impact] The PR appears safe to merge; no actionable issues were found.
Summary
Seeds fresh ARM installs into
linux-arm64-unpacked, matching where Hermes rebuilds the app.Intentional behavior acknowledged by
ryanrhughes: existing ARM copies underlinux-unpackedremain in place. The PR description assigns launcher support for both locations to the companion package change.Reviews (1) · Last reviewed commit: "Seed the Hermes app where ARM rebuilds i..." · Reviewed by Greptile