Skip to content

release: 0.7.0 - #1

Merged
lbssousa merged 4 commits into
mainfrom
release-0.7.0
Nov 3, 2026
Merged

lbssousa merged 4 commits into
mainfrom
release-0.7.0

Conversation

@lbssousa

@lbssousa lbssousa commented Nov 3, 2026

Copy link
Copy Markdown
Owner

Closes gaps that reading Omarchy PR #16100 (omacom/omarchy) showed here, and takes two more update paths out of the way of a second administrator.

Migrations

  • omarchy-mu-migrate-record@<admin>.path was only enabled by hand at install, so limited accounts could wait for good on an administrator added later. It now follows wheel (omarchy-mu-accounts sync-migration-watchers).
  • Omarchy's first setup marks every migration done without running any, so what an account has marked when it becomes an administrator no longer counts. The machine's first administrator is the exception.
  • The administrators' notice waits out a running update and counts again, and a click runs omarchy-mu-migrate, under the machine-wide lock.

Accounts

  • omarchy-mu-user-remove refuses system accounts, keeps a home holding an unfinished disk password change's note, and logs out an account with programs running, lingering included, before anything changes. When userdel removes the account but not its home, the rest still finishes.
  • omarchy-mu-user-add refuses a name whose group or /home folder exists.
  • omarchy-mu-user-admin off fails instead of saying the rights are gone when sudo -l -U still shows full sudo or the account is in docker.
  • The last administrator is the last one who can log in, and an administrator through the primary group counts.
  • Administrator checks without a user go by the session's groups, like sudo.

Update log

omarchy-mu-update-log.path moves a finished update's log to /tmp/omarchy-update.log.<owner>, also for updates started from the bar. The package enables it, and the watchers, on install and when upgrading from before 0.7.0.

Behavior change

omarchy-mu-user-remove <user> used to delete the home. Without an option it now asks, and keeping is the default answer. --delete-home is new.

Testing

just test passed with exit 0 in an archlinux container, as in CI, with all the changes together: 116 shell tests, 19 JS tests, shellcheck, qmllint, the greeter smoke test and sudoers.

The new tests fail against the old code, checked before the baseline fix was added. The account commands and the log script also ran in the container with real useradd, userdel, sudo -l -U, pkill and script(1), also before that fix.

Not tested on a real Omarchy install: the notice on screen, systemd triggering the path unit (only systemd-analyze verify), and the original fs.protected_regular failure.

Known limits

  • The bar's icon and the first-login notice still run omarchy-update outside the machine-wide lock, until Log the update transcript to a per-user path omacom/omarchy#15683 and #16100 merge upstream.
  • If a migration was pending when a new administrator was created, and the old one is removed before running it, nobody can record it, and limited accounts keep waiting. An administrator can delete their marker and run it again.

The tag is left for after the merge: just release 0.7.0 signs it with the Yubikey.

🤖 Generated with Claude Code

lbssousa and others added 4 commits November 2, 2026 20:56
Reading Omarchy PR #16100 showed what was missing here.

Migrations: omarchy-mu-migrate-record@<admin>.path was only enabled by
hand at install, so limited accounts could wait for good on an
administrator added later. It now follows wheel (omarchy-mu-accounts
sync-migration-watchers). Omarchy's first setup marks every migration
done without running any, so what an account has marked when it becomes
an administrator is set aside, except for the machine's first.

Removing refuses system accounts, asks about the home instead of always
deleting it, keeps a home holding an unfinished disk password change's
note, and logs out an account with programs running before anything
changes. When userdel removes the account but not its home, the rest
still finishes.

Adding refuses a name whose group or /home folder exists. Demoting fails
when sudo -l -U still shows full sudo or the account is in docker. The
last administrator is the last one who can log in, and administrator
checks without a user go by the session's groups, like sudo.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Upstream's notice runs omarchy-migrate, which skips the machine-wide
lock. omarchy-mu-migrate-notify now shows it itself: it waits out a
running update, counts what is still pending, and a click runs
omarchy-mu-migrate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
/tmp/omarchy-update.log blocks the next administrator's update, and the
bar's icon and the first-login notice run omarchy-update without passing
through omarchy-mu-update. omarchy-mu-update-log.path moves the log to
/tmp/omarchy-update.log.<owner> once nothing has it open.

The package enables it, and the migration watchers, on install and when
upgrading from before this version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@lbssousa
lbssousa merged commit d414cd1 into main Nov 3, 2026
1 check passed
@lbssousa
lbssousa deleted the release-0.7.0 branch November 3, 2026 00:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant