v0.5.0

Prerelease

Upgrades through pacman

Omaweb releases now go to a signed pacman repository. Add it once, and each new release arrives with your ordinary pacman -Syu.

  1. Add these lines to pacman.conf:

    [omaweb]
SigLevel = Required DatabaseRequired
Server = https://villekivela.github.io/omaweb/$arch

  2. Import the signing key with pacman-key --recv-keys and pacman-key --lsign-key.

  3. Compare the key's fingerprint with the one in the README or on the website.

  • The package in the repository is omaweb. Releases before this one shipped omaweb-git. The two conflict, so only one can be installed.
  • The repository holds one version per architecture. It serves x86_64 only. On aarch64, build from the checkout with makepkg -si until aarch64 packages are built.
  • The downloaded package and the makepkg -si build still work, for a reader who wants no third-party repository.

Release mark

Omaweb asks GitHub once a day whether a newer release is out. When one is, a mark appears in the outline footer beside the Download mark and the Sync mark. Its tooltip names the version and the command to run. Selecting it opens the release's page on omaweb.app, with the notes and how to upgrade.

  • The command follows how you installed. From the repository it is pacman -Syu. A package installed by hand is told what to install, or to add the repository. A build from a checkout is told to pull the tag and build it again.
  • Omaweb never downloads or installs a release itself.
  • The check sends nothing about the machine, and its user agent carries the release number alone.
  • A failed check is silent, and a Private window shows no mark.
  • Dismissing the mark hides it for that release only. The next release shows it again.
  • A browser left running for a week is still told.
  • A build carrying a commit count is past its tag and is never told to upgrade.
  • Turn the check off in Settings, under About.

Full changelog: https://github.com/villekivela/omaweb/compare/v0.4.0...v0.5.0

This release on GitHub