Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Enhancement Suggestion: Support sequential upgrades instead of big jumps
Reported by rsd · filed Oct 20, 2025Closed upstream on 2026-02-01. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
I upgraded one of my notebooks from Omarchy 1.x (just before the first ISO) straight to 3.1. During the install I saw a few problems — for example, an ln step failed during migration. After the upgrade, some configs and keybindings stopped working, and a few settings looked reset.
My guess is the migration expects files/state that were introduced after 1.x, so jumping directly to 3.1 skips required steps. I’ve seen similar upgrade pains on Ubuntu, Red Hat, and Mandriva; you can mitigate them, but they tend to happen with big version jumps.
Suggestion: define “destination points” (upgrade waypoints). For example: 1 → 2 only, 2 → 3, 3 → latest. Even better if the installer/docs guide or enforce that path, or run a preflight check to warn/block unsupported jumps.
View raw text
I upgraded one of my notebooks from Omarchy 1.x (just before the first ISO) straight to 3.1. During the install I saw a few problems — for example, an ln step failed during migration. After the upgrade, some configs and keybindings stopped working, and a few settings looked reset. My guess is the migration expects files/state that were introduced after 1.x, so jumping directly to 3.1 skips required steps. I’ve seen similar upgrade pains on Ubuntu, Red Hat, and Mandriva; you can mitigate them, but they tend to happen with big version jumps. Suggestion: define “destination points” (upgrade waypoints). For example: 1 → 2 only, 2 → 3, 3 → latest. Even better if the installer/docs guide or enforce that path, or run a preflight check to warn/block unsupported jumps.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.