Publish the packages omarchy depends on

[scottjones]

omarchy declares omarchy-keyring and ttf-jetbrains-mono-nerd-basic as hard depends. build-packages.sh builds both. verify() staged neither — so they were produced and thrown away on every run.

Neither exists in any repository this one carries. On a machine with omarchy-aarch64, asahi-alarm, core, extra, alarm and aur configured:

omarchy-keyring                  NOT IN ANY REPO
ttf-jetbrains-mono-nerd-basic    NOT IN ANY REPO

Machines have them only because the ISO installer put them there. Anything provisioned another way — or that loses one — cannot install or upgrade omarchy at all, because the dependency is unsatisfiable and pacman refuses the transaction. The repo did not satisfy its own dependencies.

What changed

Stage them alongside the pair, driven by what omarchy actually declares, so an omarchy that stops requiring one stops publishing it — the list can't drift from the package.

They're arch=any and carry their own upstream versions (omarchy-keyring 20251027-1, ttf-jetbrains-mono-nerd-basic 3.5.1-1), so neither the aarch64 assertion nor the RELEASE_VERSION assertion applies to them. What is enforced is that a declared dependency which failed to build stops the release, rather than publishing an omarchy nobody can install.

Recorded in packages.json as skip: true against pkgbase omarchy, the way the pair already is, since update-omarchy-mac.yml owns them rather than the generic updater.

Verified

Ran verify() as a subprocess against the real build output from the v4.0.2-2 tag — all four stage:

omarchy-4.0.2-2-aarch64.pkg.tar.xz
omarchy-keyring-20251027-1-any.pkg.tar.xz
omarchy-settings-4.0.2-2-aarch64.pkg.tar.xz
ttf-jetbrains-mono-nerd-basic-3.5.1-1-any.pkg.tar.xz

Two new self-tests: declared-and-present stages all four; declared-but-missing is rejected. 43/43 pass.

Scope

Pre-existing — these were depends of 4.0.1-2 too, so this isn't a regression from the current release work. It surfaced while checking whether anyone could receive the v4.0.2-2 update without something else they need.

Worth landing before the v4.0.2-2 publish, so the repo becomes self-sufficient in the same release rather than shipping another omarchy whose depends can't be resolved.