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.
Omarchy update does not update to the actual latest release
Reported by jcontonio · filed May 22, 2026Closed upstream on 2026-05-24 by dhh. 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
System details
Thinkpad P14s Gen 6 Intel
What's wrong?
I just ran an Omarchy update from the menu item (stable channel), and I am staring at a default Hyprland install, with zero Omarchy features, at Omarchy version 4.0.0alpha. How the hell does this happen? The update mechanism is looking at the master branch, not the tagged latest release? Ridiculous if this is the case.
An update should be safe, using Omarchy's register of packages tagged at the time of a release (3.8.1). A stable channel release should not be pulling from the master branch.
View raw text
### System details Thinkpad P14s Gen 6 Intel ### What's wrong? I just ran an Omarchy update from the menu item (stable channel), and I am staring at a default Hyprland install, with zero Omarchy features, at Omarchy version 4.0.0alpha. How the hell does this happen? The update mechanism is looking at the master branch, not the tagged latest release? Ridiculous if this is the case. An update should be safe, using Omarchy's register of packages tagged at the time of a release (3.8.1). A stable channel release should not be pulling from the master branch.
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.