Update to my earlier post, Omarchy v4.0.5. If you have OpenClaw installed and ran omarchy update after 4.0.5 landed, you may have hit “Running migration (1790397381)” followed by “Something went wrong during the update!”
What broke
4.0.5 includes a migration that moves OpenClaw from its Arch package to a self-updating copy (the “self-updating agents” line in the release notes). That needs a new OpenClaw “seed” package that hadn’t shipped yet, so the migration failed on every machine with OpenClaw installed. Because migrations stop at the first failure, the five after it never ran either, including the one that puts Omarchy’s package repo ahead of Arch’s. About 4,800 OpenClaw packages were downloaded on stable the week before release, so this isn’t a corner case.
The workaround
From the maintainer on issue #15804: mark that one migration as done, then update again from a terminal (one of the remaining migrations needs sudo):
touch ~/.local/state/omarchy/migrations/1790397381.sh
omarchy updateOpenClaw keeps working from its package and the rest of the migrations run normally.
The fix
Several PRs merged on October 18: the old migration is retired, the OpenClaw move returns as a new migration that simply finishes if the seed isn’t available yet, the seed package was merged, and npm-installed OpenClaw copies are left alone instead of failing every update. The test suite now runs migrations with the same PATH that omarchy update uses, which is the blind spot that let this through. It’s all merged but not released. v4.0.5 is still the latest, and the maintainers say the fix is coming in the next release, 4.0.6.
My take
Bugs happen. What I like is how candid the PRs are about why review missed it, and that the test gap got fixed along with the bug.
