ZacharyZhang-NY/omarchy
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify unattended updates still require sudo authorization

Browse Source
This commit is contained in:
Afonso Oliveira committed 2026-09-06 22:59:08 +01:00
1 parent 1f8f5bacac
commit a9e9954e3e
2 files changed
+3 -5
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

bin/omarchy-update
+2 -2
View File
@@ -48,8 +48,8 @@ omarchy_security_install_signal_exit_traps
omarchy-update-requires-free-space omarchy-update-requires-free-space
# -y is a promise not to ask anything. Steps that would need an answer report # -y suppresses Omarchy confirmation prompts; sudo authorization is still
# and move on instead of waiting on a prompt nobody is here to give. # required. Interactive review steps report and move on instead of waiting.
[[ ${1:-} != "-y" ]] || export OMARCHY_UPDATE_UNATTENDED=1 [[ ${1:-} != "-y" ]] || export OMARCHY_UPDATE_UNATTENDED=1
if [[ ${1:-} == "-y" ]] || omarchy-update-confirm; then if [[ ${1:-} == "-y" ]] || omarchy-update-confirm; then
docs/update-process.md
+1 -3
View File
@@ -149,9 +149,7 @@ Important behavior:
- In dev-link mode, `omarchy update` fast-forwards the active checkout from its configured upstream before changing system packages or running migrations. - In dev-link mode, `omarchy update` fast-forwards the active checkout from its configured upstream before changing system packages or running migrations.
- Migrations remain in chronological order even though historical entries mix user-controlled code with later privileged repairs. Before entering that mixed-trust tail, Omarchy invalidates its timestamp and forces every later sudo call—including AUR's configurable sudo command—to use `--no-update`; prompts authorize one command without publishing a reusable timestamp. Yay's credential loop is disabled for the update. - Migrations remain in chronological order even though historical entries mix user-controlled code with later privileged repairs. Before entering that mixed-trust tail, Omarchy invalidates its timestamp and forces every later sudo call—including AUR's configurable sudo command—to use `--no-update`; prompts authorize one command without publishing a reusable timestamp. Yay's credential loop is disabled for the update.
- User-controlled post-update hooks and mise tools run only after every sudo-capable update stage. Omarchy invalidates its sudo timestamp before each boundary and on every exit; detached children therefore have no later reusable update authorization to wait for. - User-controlled post-update hooks and mise tools run only after every sudo-capable update stage. Omarchy invalidates its sudo timestamp before each boundary and on every exit; detached children therefore have no later reusable update authorization to wait for.
- `-y` exports `OMARCHY_UPDATE_UNATTENDED=1` — a promise not to ask anything. - `-y` exports `OMARCHY_UPDATE_UNATTENDED=1` and suppresses Omarchy confirmation prompts. Interactive review steps (orphan removal, conflict handoff) report and skip instead of blocking. Privileged commands still require sudo authorization, and command-scoped authentication can prompt separately for each command.
Steps that would prompt (orphan removal, conflict handoff) report and skip
instead of blocking.
- The free-space requirement uses a 10 GiB threshold and stops the update before - The free-space requirement uses a 10 GiB threshold and stops the update before
confirmation when it is not met. If free space cannot be determined, the confirmation when it is not met. If free space cannot be determined, the
check is silently skipped. Set `OMARCHY_UPDATE_FORCE=1` to bypass the check. check is silently skipped. Set `OMARCHY_UPDATE_FORCE=1` to bypass the check.