Files
omarchy/migrations
Spencer Bull 73b4fc0d8a Rename the Elsewhen migration so the link repair reaches machines that already ran it
The re-point of a user plugin link stranded by the elsewhen package moving from plugins/ to shell/plugins/ landed in migration 1789581661, which every machine updated between that migration shipping and the package moving had already applied. omarchy-migrate keys completion on the filename alone, so the repair never ran where it was needed. On a dev checkout the shell discovers the packaged plugin only through that link, and a rescan drops a dangling one, so Elsewhen vanished from the bar on the first shell start after the package upgrade.

Renaming the file runs the whole migration again everywhere. Each step is safe to repeat: the package add is a no-op once installed, both link branches are guarded, the rescan is best-effort, and the put keeps an existing placement. The new test holds a state directory with only the old marker and checks the renamed file is still pending, which the old name could not pass.
2026-09-21 21:14:46 -05:00
..
2026-06-12 13:49:46 -04:00
2026-06-12 13:49:46 -04:00
2026-06-12 13:49:46 -04:00
2026-06-12 13:49:46 -04:00
2026-06-12 13:49:46 -04:00
2026-06-12 13:49:46 -04:00
2026-06-29 08:51:15 -05:00
2026-06-20 15:44:37 -04:00
2026-06-21 02:25:42 -04:00
2026-06-21 12:31:06 +02:00
2026-07-19 09:59:13 -07:00
2026-07-24 19:49:13 -07:00
2026-07-28 21:07:50 -04:00
2026-07-29 12:27:38 -07:00
2026-08-01 21:56:51 -05:00
2026-08-01 19:32:32 -07:00
2026-08-11 13:56:09 +02:00
2026-09-05 23:28:46 -05:00
2026-09-13 16:59:33 +02:00