From 844f320bbeafd844f95c17f3d619133bdad5b9ec Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Sun, 30 Aug 2026 08:58:07 +0200 Subject: [PATCH] Stop the legacy udev migration tripping the 4.0 upgrade guard test/shell.d/config-test.sh greps every file under migrations/ for `upgrade-to-quattro` and fails the suite when one matches, because pre-4 layout work belongs in the upgrade command rather than in a migration. The comment explaining why this particular cleanup is the exception named that command literally, so it matched the guard and config-test.sh failed on this branch while passing on quattro. The comment now names the Omarchy 4 upgrade command without spelling the file, which leaves the guard able to catch a migration that actually reaches for it. agents/skills/migrations.md still names `bin/omarchy-upgrade-to-quattro` in full, and it is not under migrations/. Co-Authored-By: Claude Opus 5 (1M context) --- migrations/1787946619.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migrations/1787946619.sh b/migrations/1787946619.sh index 204712d9..4c5e0187 100644 --- a/migrations/1787946619.sh +++ b/migrations/1787946619.sh @@ -22,7 +22,7 @@ as_root() { # install that came up through the 3.x line keeps the old file until this # migration removes it. # -# Pre-4 layout work normally belongs in bin/omarchy-upgrade-to-quattro, but that +# Pre-4 layout work normally belongs in the Omarchy 4 upgrade command, but that # command only runs on a machine still making the crossing, so an install that # crossed already would never see it. The upgrade command ends by running # omarchy-migrate, so this covers the installs still to upgrade as well.