Skip to content

Support package-managed Aether updates - #131

Merged
bjarneo merged 4 commits into
omacom:mainfrom
AFOliveira:fix/package-managed-updates-20260926
Oct 4, 2026
Merged

bjarneo merged 4 commits into
omacom:mainfrom
AFOliveira:fix/package-managed-updates-20260926

Conversation

@AFOliveira

Copy link
Copy Markdown
Member

Allow distributions to set a package update command at build time. Managed builds skip release checks, refuse direct self-upgrades and avoid launching the terminal updater; the CLI and desktop indicator direct users to the package manager instead.

The private linker setting is -X aether/internal/update.packageUpdateCommand=omarchy-update. Leaving it empty preserves the standalone update behavior.

Validation: full Go tests, managed-build CLI tests, focused frontend tests and Svelte checks pass. The corresponding Omarchy package was exercised through its CLI and GUI in a disposable x86_64 VM.

This provides a distribution update policy. Authenticating artifacts in the standalone updater remains separate work.

Signed-off-by: Afonso Oliveira <afonso.oliveira707@gmail.com>
Signed-off-by: Afonso Oliveira <afonso.oliveira707@gmail.com>
The build-time setting had no effect on the Omarchy and AUR packages,
because both install the release binary. Aether now asks pacman whether
it owns the running executable. When it does, Aether skips release
checks and refuses self-upgrades, and aether upgrade prints the update
command. The -X packageUpdateCommand setting still overrides the check.

Hide the release indicator in managed installs, so the header does not
show a dot that never changes.
# Conflicts:
#	frontend/src/lib/components/layout/ReleaseIndicator.svelte
@bjarneo
bjarneo merged commit 29d07b1 into omacom:main Oct 4, 2026
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.

2 participants