Commit Graph
100 Commits
Author SHA1 Message Date
Ryan Hughes ca63e47ecd Stop auto-syncing retroarch-joypad-autoconfig-git from the AUR
The package carries a deliberate commit pin (59d557a) so every
architecture packages the same tree. The AUR sync kept trying to revert
that to the unpinned branch-tip recipe, recording a version downgrade in
the process. Mark it local so exactly one source owns the recipe; it is
Omarchy-maintained until it moves to an upstream release feed.
2026-09-07 01:23:14 -04:00
Ryan Hughes 2a3b3b9c36 Merge pull request #322 from btsouth/omakade-1.6.1
omakade: update to 1.6.1 with full runtime deps and aarch64
2026-09-07 00:02:13 -04:00
Ryan Hughes 34c12d99c7 Merge pull request #313 from omacom/auto/sync-upstream
chore: sync upstream releases
2026-09-06 23:52:53 -04:00
Ryan Hughes cb85e6d289 Merge pull request #331 from omacom/fix/locate-service-defaults
Package the locate service defaults
2026-09-06 21:52:39 -04:00
Ryan Hughes 397cf6f527 Package the locate service options 2026-09-06 21:46:40 -04:00
Ryan Hughes b81d678b3f Merge pull request #320 from omacom/fix-check-versions-carch
Read PKGBUILDs with CARCH set; unblock the channels stuck on 1password
2026-09-05 17:08:58 -04:00
Ryan Hughes d673d67a1c Read PKGBUILD variables with CARCH set and refuse to queue a package whose version cannot be read
makepkg always exports CARCH, so PKGBUILDs may branch on it at file
scope. Every place the tooling sourced a PKGBUILD did so without CARCH,
taking the wrong branch or aborting partway, and check-versions turned
the resulting empty pkgver/pkgrel into the version '-', which never
matches a published version and queues an endless rebuild.

package_pkgbuild_var reads one variable the way makepkg would see it,
for the architecture being checked, and reports whether the source
succeeded. check-versions, sync-rebuilds and omarchy-pkgs use it.
check-versions now warns and skips a package whose pkgver or pkgrel is
empty instead of comparing a partial version. A self-test covers a
PKGBUILD that branches on CARCH before assigning its version.
2026-09-05 16:59:22 -04:00
Ryan Hughes d57a9955d5 1password: map the tarball architecture inside package() so the PKGBUILD's version can be read without CARCH
The file-scope case on CARCH ended in 'return 1', which aborted any
'source PKGBUILD' that did not export CARCH before pkgver and pkgrel
were assigned. check-versions reads PKGBUILDs that way, saw an empty
version, queued 8.12.34-35 on every tick, and promotion then refused to
overwrite the already-published artifact. Every channel has been in
backoff since 06:41 UTC today because of it.
2026-09-05 16:59:22 -04:00
Ryan Hughes cb7a1a8868 Merge pull request #317 from omacom/add-omareel
Add omareel, a screen recorder and editor for Omarchy
2026-09-05 15:27:46 -04:00
Ryan Hughes 2944f5e802 omareel: pin the v0.1.0 archive checksum 2026-09-05 14:47:12 -04:00
Ryan Hughes 3682eaf718 Add omareel, a screen recorder and editor for Omarchy 2026-09-05 14:20:51 -04:00
Ryan Hughes fe0a3da325 Merge pull request #312 from omacom/fix/upstream-sync-git-dependency
Fix missing Git in upstream sync container
2026-09-05 02:36:11 -04:00
Ryan Hughes 7397d1fbfd Install Git for upstream syncs 2026-09-05 02:28:08 -04:00
Ryan Hughes bceab72f8c Merge pull request #277 from maralcbr/omacom/aarch64-host-pipeline
Make aarch64 a first-class architecture in the scheduled pipeline
2026-09-05 02:24:36 -04:00
Ryan Hughes ca99c24b01 Add ARM builds for 1Password and Voxtype 2026-09-05 01:09:11 -04:00
Ryan Hughes de57b5dfc2 Publish only intended package artifacts 2026-09-05 00:07:11 -04:00
Ryan Hughes 520dd5c3bb Repair aarch64 package coverage 2026-09-04 23:40:49 -04:00
Ryan Hughes 0b67dbab8e Harden emulated ARM builds 2026-09-04 23:40:49 -04:00
Ryan Hughes 9e9acb071a Support rootless Podman builds 2026-09-04 23:40:49 -04:00
Ryan Hughes 76687fcc82 Harden multi-architecture release pipeline 2026-09-04 23:40:49 -04:00
Ryan Hughes 7860c4b2e4 Merge pull request #195 from oceanapplications/aarch64-arch-support
Own and build nine ARM-compatible packages
2026-09-03 22:19:39 -04:00
Ryan Hughes b89770c1da Expand declarative upstream providers 2026-09-03 22:13:59 -04:00
Ryan Hughes d9705d0e2f Own ARM-compatible recipes and sync upstream directly 2026-09-03 22:04:04 -04:00
Ryan Hughes c3c1f8fbab Merge pull request #276 from maralcbr/omacom/builder-flags
Add builder flags for CI and resumed builds
2026-09-03 21:52:12 -04:00
Ryan Hughes a2e29a9463 Merge pull request #275 from maralcbr/omacom/pkgbuild-portability
Build the omarchy package pair for aarch64
2026-09-03 21:52:08 -04:00
Ryan Hughes 18f11555b6 Merge pull request #226 from jeremydixon22/update/jetbrains-mono-nerd-3.5.1
Update JetBrains Mono Nerd Font to 3.5.1
2026-09-03 19:23:15 -04:00
Ryan Hughes 0d803dd825 Merge pull request #236 from omacom/auto/sync-rebuilds
chore: rebuild against updated dependencies
2026-09-03 19:08:42 -04:00
Ryan Hughes 7f9726c00e Merge pull request #291 from omacom/sync-flea-0.1.3
Update Flea to 0.1.3
2026-09-03 18:06:57 -04:00
Ryan Hughes 05a4119b43 Update Flea to 0.1.3 2026-09-03 18:05:52 -04:00
Ryan Hughes 0d94ae5b38 Merge pull request #261 from omacom/auto/sync-upstream
chore: sync upstream releases
2026-09-03 15:10:41 -04:00
Ryan Hughes 1dfa9be45b Merge pull request #273 from omacom/auto/sync-aur
chore: sync AUR packages
2026-09-03 15:10:14 -04:00
Ryan Hughes 96f3a194e1 Merge pull request #290 from omacom/fix-flea-builder-tests
Fix Flea tests in constrained builders
2026-09-03 14:23:38 -04:00
Ryan Hughes 89e6e4d1cc Fix Flea tests in constrained builders 2026-09-03 14:20:07 -04:00
Ryan Hughes 3a78ac6eb4 Merge pull request #289 from omacom/add-strata-upstream-sync
Add safe upstream release sync for Strata
2026-09-03 14:16:32 -04:00
Ryan Hughes fc27de8a2e Add safe upstream sync for Strata 2026-09-03 14:03:25 -04:00
Ryan Hughes dcb8211050 Merge pull request #288 from omacom/add-flea-fast-ring
Add hardened Flea package to fast ring
2026-09-03 13:57:06 -04:00
Ryan Hughes 09e41d7d88 Add hardened Flea package 2026-09-03 13:41:54 -04:00
Ryan Hughes 48e60a6539 Merge pull request #281 from omacom/add-strata-fast-ring
Add Strata file manager to fast ring
2026-09-03 00:44:35 -04:00
Ryan Hughes 1e6cde3916 Add Strata file manager 2026-09-03 00:43:30 -04:00
Ryan Hughes b66905a437 Drop t3code-patched-bin
The environment-theme patches shipped as a forked AppImage while
upstream lacked them. Keeping it current means a hand-built artifact
per release, and it has fallen three behind — 0.0.35 against 0.0.38.

t3code-bin tracks the upstream feed on its own, so drop the fork.
Nothing else in the repo referenced the package.
2026-09-01 23:55:52 -04:00
Ryan Hughes d562ecb388 t3code-bin: 0.0.38 2026-09-01 23:55:52 -04:00
Ryan Hughes b0cba5bf8b Drop obsolete asusctl 6.4.0 GitHub-source patch (#269)
The AUR caught up: asusctl 6.4.0-1 (b0ec6ca) repoints source at the
GitHub repo upstream, which is what our patch existed to do. The new
PKGBUILD uses a release tarball instead of git+, so the patch context
no longer matches and every scheduled Sync AUR Packages run failed
applying it.

Remove the patch and resync from the AUR. With no .omarchy/patches
left, the package is no longer customized, so it tracks 6.4.0-1
without the .1 pkgrel suffix.
2026-09-01 23:30:10 -04:00
Ryan Hughes 6774df1001 Merge pull request #259 from omacom/auto/sync-upstream
chore: sync upstream releases
2026-09-01 10:38:15 -04:00
Ryan Hughes 8550bd3124 Merge pull request #258 from omacom/auto/sync-aur
chore: sync AUR packages
2026-09-01 10:38:04 -04:00
Ryan Hughes a3d150e2b0 Merge pull request #253 from omacom/add-link-studio-opr
Add Link Studio to the fast ring
2026-09-01 02:01:09 -04:00
Ryan Hughes 2fad766013 Add Link Studio to the fast ring
Package Link Studio 1.0.2 with its AUR-only MediaPipe and sounddevice dependencies. Wire Link Studio to GitHub release checksums, keep all three packages on the fast ring, and make MediaPipe's Bazel bootstrap a checksummed makepkg source.
2026-09-01 01:55:23 -04:00
Ryan Hughes c6e34f7949 Merge pull request #252 from omacom/add-omakade-opr
Add Omakade to the fast ring
2026-09-01 01:51:10 -04:00
Ryan Hughes a42235e1a5 Add Omakade to the fast ring
Build the upstream 1.2.0 source release for x86_64 and follow stable GitHub releases through the published SHA256SUMS manifest.
2026-09-01 01:25:44 -04:00
Ryan Hughes 899d5030ce Merge pull request #231 from omacom/auto/sync-upstream
chore: sync upstream releases
2026-09-01 01:24:52 -04:00
Ryan Hughes eace5f13a9 Merge pull request #230 from omacom/auto/sync-aur
chore: sync AUR packages
2026-09-01 01:24:29 -04:00
Ryan Hughes 9995058806 Merge pull request #235 from jethrojones/add-omapresent-package
Add omapresent Markdown presentation package
2026-09-01 01:22:08 -04:00
Ryan Hughes e934aa9ee2 Mark omapresent for fast release ring 2026-09-01 01:21:34 -04:00
Ryan Hughes 28a4cfc662 Make release publication fail closed 2026-08-30 23:49:27 -04:00
Ryan Hughes 246eea9620 Fix Hermes Desktop keyring detection on Hyprland
Default Electron to the gnome-libsecret password store so Hermes can use GNOME Keyring for secure remote tokens. Declare libsecret as a runtime dependency.
2026-08-30 23:49:02 -04:00
Ryan Hughes 4c41157163 Release omarchy 4.0.2 2026-08-30 23:22:02 -04:00
Ryan Hughes 8bfa054676 Cut the rc ISO under its numbered candidate version
cmd_rc handed maybe_iso the bare train version, so omarchy-iso-release
named every candidate omarchy-X.Y.Z-rc.iso — rc2 uploaded over rc1's
URL. Pass the pinned rcN version instead; paired with omarchy-iso's
f9be60b, the artifact becomes omarchy-4.0.2rc2.iso. The ship path
keeps passing the final version.
2026-08-30 17:15:52 -04:00
Ryan Hughes cb84ec0e69 Pin omarchy 4.0.2rc2 on master so edge carries it
Edge is the channel the 4.0.2 RC ISOs point pacman at until the rc-channel
migration lands, but edge only carried omarchy 4.0.1 — older than the
installed 4.0.2rc1, so those installs never saw an upgrade. Bumping master's
pin lets the normal edge pipeline build and publish 4.0.2rc2, whose migration
repoints [omarchy] at the rc channel.

Stable is unaffected: pinned packages never build for stable
(package_builds_for_mirror), it only receives them via the rc->stable advance
at ship time.

(cherry picked from rc-branch pin commit 11767d6)
2026-08-30 16:26:37 -04:00
Ryan Hughes 82b28bb6f3 Bust the CDN cache when reading published channel dbs
pkgs.omarchy.org sits behind Cloudflare, and right after a sync the
plain db URL keeps serving the previous file from the edge cache
(observed: a cache HIT with age 900s+ returning the pre-release db).
That made status report the old version, wait_for_published poll a
frozen file for its full timeout, and would let RC auto-numbering
count from last release's versions. A unique query string per fetch
skips the cached entry.
2026-08-30 13:35:44 -04:00
Ryan Hughes bde81c757c Forward OMARCHY_RC_PINS into the build container
package_builds_for_mirror gates pinned packages' rc builds on
OMARCHY_RC_PINS, but that check runs inside the container via
build.sh, and docker run only forwarded ARCH/MIRROR/PACKAGES —
so the rc trigger's pinned builds were always skipped as 'not
configured for direct rc builds'.
2026-08-30 13:27:32 -04:00
Ryan Hughes 00dd64db61 Accept multiple package names in bin/release --package
The rc trigger passes '--package omarchy omarchy-settings', and bin/build
already consumes every name up to the next --option, but bin/release only
took one — the second name fell through to 'Unknown option' and the
release exited before building anything. Parse greedily, like bin/build.
2026-08-30 13:25:13 -04:00
Ryan Hughes 4a87a738b2 Number asdcontrol's sudoers policy and add it to the fast ring (#243)
* Use a numbered asdcontrol sudoers priority

* Add asdcontrol to the fast ring
2026-08-30 13:02:46 -04:00
Ryan Hughes 30d03c4d26 Scope asdcontrol's passwordless sudo grant (#242)
Ship the least-privilege rule with asdcontrol so authorization follows the package lifecycle. Install it after older broad rules for safe staggered upgrades.
2026-08-30 12:59:21 -04:00
Ryan Hughes cf39173553 Revert "Add hey-cli to the fast ring"
This reverts commit 3bfc267a0e.
2026-08-29 13:36:56 -04:00
Ryan Hughes 3bfc267a0e Add hey-cli to the fast ring 2026-08-29 12:09:48 -04:00
Ryan Hughes 6daa7c90e4 Stage CUPS authorization as settings override (#237) 2026-08-29 02:19:29 -04:00
Ryan Hughes 391b5a201f t3code-patched-bin: 0.0.35-5, rebuilt from v0.0.35-omarchy.5 2026-08-28 22:33:11 -04:00
Ryan Hughes 4776db7f31 Merge pull request #213 from jeremydixon22/fix/asusctl-6.4.0
Update asusctl to 6.4.0
2026-08-28 18:31:57 -04:00
Ryan Hughes f48d528ca4 t3code-patched-bin 0.0.35-4: rebuild after review
Same upstream release, so only pkgrel moves. Built from v0.0.35-omarchy.4,
which carries the fixes from nine rounds of review on the upstream PR: the
CLI no longer overwrites an unreadable settings.json, setting a
single-appearance theme actually switches the client, reconnects no longer
flash published themes back to stock, and already-shipped clients keep
their config subscription instead of losing it to an unknown event.
2026-08-28 17:46:51 -04:00
Ryan Hughes a8c9e2982e Stop pick from hiding long-lived PRs behind a creation-ordered window
`gh pr list` orders by creation date, so `--limit 30` cut the candidate set by
when PRs were opened, not when they merged. The `sort_by(.mergedAt)` that
followed only reordered whatever survived that cut. A PR opened before the
window but merged inside it — exactly the kind a release branch still needs —
never reached the already-on-branch check at all. #7649 and #7709 were both
missing from v4-0-2's list for this reason.

The window is now bounded by the branch point instead of a count: pull a wide
page and keep what merged after the merge-base's commit date, since anything
merged into the dev branch before the release branch left it is already there
by ancestry. v4-0-2 went from 11 candidates to 31.

Widening it surfaced a second gap. A change re-applied by hand carries neither
a PR number nor a cherry-pick trailer, so already_on_branch could not see it
and offered it again (#6939, applied as 33d7363c). It now also compares the PR
title against the branch's subjects, with any trailing "(#N)" stripped.
2026-08-28 15:13:58 -04:00
Ryan Hughes f84c89d8b3 t3code-patched-bin: record the full artifact-shipping recipe
Comment-only. The .env requirement and the fact that only a PKGBUILD
version change triggers the build server both bit us once each; the
recipe now lives where the next rebuild starts.
2026-08-28 01:32:02 -04:00
Ryan Hughes dd8fd2fed7 t3code-patched-bin 0.0.35-3: bake T3 Connect public config
The r2 artifact was built without the public Connect configuration official
artifacts carry (relay URL, Clerk publishable key, CLI OAuth client id), so
Connect prompted for login with no way to log in. Same code, rebuilt with
the configuration recovered from the published npm t3 package.
2026-08-28 01:27:55 -04:00
Ryan Hughes 267dbdefaa t3code-patched-bin 0.0.35-2: post-review rebuild, fast ring
Rebuilt from v0.0.35-omarchy.2 of the environment-theme branch: the stream
event is capability-gated so old clients keep their config subscription,
republish dedupe is structural, the connect stream is gap-free, default
adoption is scoped per environment and keyed on the set generation, and
reserved theme ids cannot be published over. Joins the fast ring like
t3code-bin so patch rebuilds reach machines quickly.
2026-08-28 01:07:37 -04:00
Ryan Hughes 0fb1c09041 t3code-patched-bin: T3 Code with the environment-theme patches
Built from the environment-theme branch of ryanrhughes/t3code (tag
v0.0.35-omarchy.1) until upstream ships it: the app follows themes the
machine publishes into its state directory -- Omarchy retints it live --
and t3 theme set works. Same packaging as t3code-bin, conflicts with it,
and the next upstream release supersedes it after a rebase.
2026-08-27 23:55:15 -04:00
Ryan Hughes 273dd810da t3code-bin: ship the bundled server CLI as /usr/bin/t3
The desktop bundle already contains the full server -- the same entrypoint
npm's t3 package runs -- so a launcher that starts it through the bundled
Electron as Node puts the CLI on PATH without a second runtime. Upstream
only distributes the CLI via npm, which Omarchy's install scripting cannot
assume.
2026-08-27 23:55:15 -04:00
Ryan Hughes 01a95d9c28 Merge pull request #217 from fvdb/update-grok-bot-0.29.0
Update grok-bot to 0.29.0
2026-08-27 23:27:32 -04:00
Ryan Hughes 02d0c4ccd1 Merge pull request #225 from omacom/auto/sync-upstream
chore: sync upstream releases
2026-08-27 23:27:03 -04:00
Ryan Hughes 9ebab47ed4 Merge pull request #224 from omacom/auto/sync-aur
chore: sync AUR packages
2026-08-27 23:26:50 -04:00
Ryan Hughes dbb5e72051 Build fast-ring for rc as rc, instead of copying stable's artifacts
The rc channel's Arch base can sit anywhere between stable's snapshot and
edge's, so a package built against stable's libraries is not necessarily
correct for rc. Copying stable's fast-ring artifacts into rc therefore shipped
possibly-mislinked packages to RC testers. Fast-ring packages now build
natively for all three channels, each in its own image against its own base
mirror, and the stable release's replication step is gone.

That required separating 'may be built here' from 'whose version wins'. The
release pair is now marked "pinned": its version is set per release on the rc
branch, so it builds for rc only from that branch's worktree
(OMARCHY_RC_PINS=1, set by omarchy-release rc) — master's shipped pins can
never overwrite an in-flight RC, even though check-versions now discovers rc
work like it does for edge and stable.
2026-08-27 12:39:29 -04:00
Ryan Hughes 9fd75fc3ba Report the stable publish before the rc parity copy, and quiet the copy
The fast-ring replication announced itself before the release that triggered
it, so chat read as though an rc job had run on its own — the reverse of what
happened. The publish report now fires first, and the replication says only
how many packages were kept in parity: the release report immediately above it
already lists them by name.
2026-08-27 12:21:41 -04:00
Ryan Hughes 370c37670b Merge pull request #211 from tobi/update-omasnap-1.20.0
omasnap: update to 1.20.1
2026-08-27 11:01:26 -04:00
Ryan Hughes 23739852a5 Merge pull request #207 from omacom-io/auto/sync-upstream
chore: sync upstream releases
2026-08-27 11:01:21 -04:00
Ryan Hughes f8156190b1 Merge pull request #206 from omacom-io/auto/sync-aur
chore: sync AUR packages
2026-08-27 11:01:17 -04:00
Ryan Hughes aa0a836c1c Update README for the three-channel pipeline and remote control
Sections that still described the old two-channel, host-only world:

- command scope: the host-tree commands forward over ssh now, and advance
  replaces the deprecated migrate
- global flags: --mirror takes edge|rc|stable, and --local exists
- build examples and directory structure: the rc channel and the release lock
- release section: omarchy-release is the front door; omarchy-pkgs is the pin
  engine it drives (and still usable directly)
- management: bin/repo timers, the backoff state files, and clearing a stale
  lock, instead of raw systemctl invocations that omitted the rc units
- a leftover reference to the 6-hourly timer as the trigger backstop

Also fixed an anchor that pointed at the section containing the link rather
than the Quick Start section it names.
2026-08-27 01:40:05 -04:00
Ryan Hughes 1512cb48d8 chore: sync t3code-bin to 0.0.34
Matches what is already published to edge: 0.0.34 was built on the server
before the bump reached git, so the checkout read as out of date and queued a
rebuild of the older 0.0.33-2 that promotion then refused. Produced by
bin/sync-upstream, the same path the scheduled workflow uses.
2026-08-27 01:16:55 -04:00
Ryan Hughes 5d501f8ef9 Stop treating a single shared chat as a misconfiguration
Reporting to BASECAMP_CHATBOT_URL is a working setup — the second variable
exists only for those who want release traffic in its own chat. setup now
states which chat receives reports instead of warning about the common case,
and the README frames the split as optional rather than expected.
2026-08-27 01:15:06 -04:00
Ryan Hughes 7c3cfc50e9 Fix silent notifications and stop stale checkouts queueing rebuild loops
Two failures from the first live run:

notify_basecamp declared 'local BASECAMP_CHATBOT_URL' and then called
release_chatbot_url, whose fallback reads that same global — bash locals are
visible to called functions, so the fallback saw the empty local and every
notification silently went nowhere for anyone with only the legacy variable
set. The local is now named 'url'.

check-versions compared PKGBUILD and published versions with !=, so a checkout
BEHIND the channel queued a rebuild of an older version every cycle: the
builder produced it and promotion refused it, because that exact filename is
already published with different bytes. It now skips (with a warning naming
the package) when an artifact for the PKGBUILD's version already exists in the
channel, whichever direction the versions differ.
2026-08-27 01:10:33 -04:00
Ryan Hughes 0eb592b624 Stop the rc unit failing before the first RC is cut
The rc service fetched and reset /root/omarchy-pkgs-rc in ExecStartPre, but
that worktree does not exist until the first RC creates the rc branch — so on
a freshly set up host the unit failed every five minutes, forever, and showed
up as a failed unit in the timer report.

It now runs bin/auto-release-rc from the main checkout, which always exists:
nothing queued exits silently, no rc branch is a clean no-op, and a missing
worktree is created on demand before handing off to the worktree's own
auto-release.
2026-08-27 01:10:33 -04:00
Ryan Hughes af1b9c7791 Restore README truncated in 74f0959, with both reporting edits applied
A bad in-place edit truncated the file to zero: open(p,'w') ran before
open(p).read(), so the read saw an already-empty file. Restored from c0a63dd
and reapplied the two intended changes — the start report now naming queued
packages, and the nothing-to-publish report described as the check/builder
disagreement signal it is.
2026-08-27 01:10:33 -04:00
Ryan Hughes f551ab922c Report queued runs that publish nothing, as the anomaly they are
Restores the no-change report now that it is clear it cannot fire on an idle
timer tick: releases only run when the version check queued work, so a run
that publishes nothing means check-versions and the builder disagree about
what is out of date. The report names the packages that were queued but never
built, so a recurring disagreement is diagnosable rather than invisible.
2026-08-27 01:10:33 -04:00
Ryan Hughes cb986c0985 Drop no-change reports; name the queued packages when a build starts
A release that published nothing is not news, and at a 5-minute cadence those
messages would bury the ones that matter — the log and bin/repo timers still
show the run happened.

Removing it would have left a start report with no follow-up, so the start
report now carries its own answer: check-versions writes the package names it
queued into the state file instead of touching an empty one, and the release
run reads them. 'A build is running' becomes 'your package is in this build',
which is the question the reports exist to answer.
2026-08-27 01:10:33 -04:00
Ryan Hughes e3c3b3e50a Report build starts and successes, not just failures, to their own chat
Only failures were reported, so a push could reach the mirror with no way to
know short of querying the database by hand. Release runs now report:

- start: channel, arch, host, and the commit being built
- published: the packages and versions that went out, duration, channel URL
- no-changes: the run found nothing to build
- promoted: what advance moved between channels, including the rc bootstrap
  and fast-ring replication
- failed: unchanged, plus the commit context the other reports carry

Release traffic goes to OMARCHY_RELEASE_CHATBOT_URL, falling back to
BASECAMP_CHATBOT_URL, so build reports stop drowning the repository chat the
sync workflows post to. bin/setup reports which destination is configured.

The published list is captured after the build step because promote moves the
files out of build-output, and is capped at 25 entries so a full rebuild does
not produce an unreadable wall of chat.
2026-08-27 01:10:33 -04:00
Ryan Hughes 71e72e581b Run the timers every 5 minutes, with overlap and failure guards
A push reaching the mirror should take minutes, not up to six hours. All four
units now fire every 5 minutes, staggered a minute apart. Three guards make
that cadence safe:

- Scheduled runs take the release lock NON-BLOCKING (try_release_lock) and
  skip the tick when a build is running. Blocking would stack one stalled
  process per tick behind a long build and stampede when it finished. Manual
  commands still wait, as an operator expects.
- check-versions takes the lock too, and now owns its git pull (--pull, passed
  by the unit) instead of an ExecStartPre: at this cadence an unlocked pull
  would swap PKGBUILDs out from under a running build.
- A failed release records .build-failed-<channel> and backs off
  exponentially (10m, 20m, 40m … capped at 6h) rather than rebuilding the same
  broken tree every 5 minutes. Any new commit clears the backoff, since a push
  is the most likely fix.

Idle ticks exit without output so the journal keeps showing the runs that
matter, and bin/repo timers reports backoff state — a paused channel is
otherwise indistinguishable from an idle one.
2026-08-27 01:10:33 -04:00
Ryan Hughes 9d86123264 Add bin/repo timers: release timer and queue status at a glance
Wraps systemctl list-timers with the things you actually want when checking on
the build host: per-unit enabled state, last run and whether it succeeded,
which channels have builds queued (state files), whether the release lock is
held by a live process, and any failed units. Units are discovered from
systemd/*.timer so the report cannot drift from what setup installs.

It forwards over ssh like the other host commands, so the build box's timer
state is one command away from a workstation (--local to inspect this machine).
2026-08-27 01:10:33 -04:00
Ryan Hughes db816061a6 setup --check: distinguish a missing rc worktree from no rc branch yet
--check warned 'rc worktree would be created' whenever the directory was
absent, implying a plain setup run would create it — but with no rc branch in
existence setup skips it, so the warning described something that would not
happen and asked for action that was not possible. It now reports the branch
state: present, would-create (branch exists), or nothing-to-do (no branch
yet — the first RC cut creates the branch and the build trigger creates the
worktree on demand). Branch detection is read-only, as --check must be.
2026-08-27 01:10:33 -04:00
Ryan Hughes 0393849285 bootstrap-rc: seed the release pair into rc, not just the promoted set
Eligibility used package_moves_to_channel, which excludes packages built
natively in the destination — right for ongoing edge -> rc advances (a native
build must not be raced under the same filename) but wrong for the bootstrap,
whose entire purpose is rc == stable. omarchy and omarchy-settings were
therefore left out, so a machine switched to the rc channel could not install
or update the release pair until the first RC was cut. The bootstrap now
requires only destination membership; nothing is built in rc yet, so there is
no native artifact to conflict with. The dev pair stays edge-only and
fast-ring replication is unchanged.
2026-08-27 01:10:33 -04:00
Ryan Hughes e50f868a10 Channel-correct Docker images: keyring from own channel; repo-add uses edge
The builder stage never declared ARG MIRROR, so the keyring [omarchy] repo
pointed at the channel-less legacy pkgs.omarchy.org/$arch path — it works
only because a stale copy of the old layout still answers there, and it would
miss a keyring rotation. Each image now pulls omarchy-keyring from its own
channel (edge/rc/stable), matching the base mirror it already selects.

update-repo and remove-package switch to the edge x86_64 image: repo-add and
repo-remove compile nothing, and using the channel image would deadlock
bootstrap-rc — the rc image can only build once the rc channel it pulls the
keyring from exists remotely.
2026-08-27 01:10:33 -04:00
Ryan Hughes 49ca22fa9f bin/repo becomes a remote control: forward host-tree commands over ssh
With a repository host configured (OMARCHY_REPO_HOST / .repo-host), release,
build, sign, promote, update, clean, advance, bootstrap-rc, remove, sync, and
migrate exec on the host over ssh — same code, run where the published tree
lives, after sourcing the host credentials and a --ff-only pull. --local
forces local execution. list/push/deploy/setup never forward. The host itself
has no .repo-host, so ssh'd-in manual use is unchanged. omarchy-release's
advance now rides the same forwarding (one code path), and --host exports
OMARCHY_REPO_HOST so child bin/repo calls follow it.

This closes the gap where bootstrap-rc ran against a workstation's stale
local tree despite .repo-host being set.
2026-08-27 01:10:33 -04:00
Ryan Hughes 161eecd5ff Explicit host config outranks the local build-host inference; document it
The published-db marker also exists on any workstation that once ran a full
local release, so --host / OMARCHY_REPO_HOST / .repo-host are now checked
before on_repo_host everywhere (triggers, advances, doctor). README documents
the detection, the caveat, and the .repo-host tie-breaker.
2026-08-27 01:10:33 -04:00
Ryan Hughes 52475c4bbc Run host operations locally when this machine is the build host
Release commands now work from anywhere: on_repo_host (the published database
living in this checkout) routes build triggers, advances, and promotion to
local execution; other machines go over ssh to the configured destination.
The host setting is any ssh destination — root@<ip>, root@<hostname>, or an
~/.ssh/config alias — resolved from --host, OMARCHY_REPO_HOST, then the
one-line .repo-host file. doctor reports which mode applies, and the README
documents the format and precedence. All host connections are plain ssh.
2026-08-27 01:10:33 -04:00
Ryan Hughes a5cafb291c Push over SSH from the tmp clones; keep reads on anonymous HTTPS
The work/mirror clones were HTTPS end to end, so pushes went through git's
credential-helper config — which breaks the moment a stale absolute gh path
is baked into it (as gh auth setup-git once did with /usr/bin/gh). Reads stay
anonymous HTTPS; pushes now use an SSH push URL (derived from the clone URL,
overridable with OMARCHY_UPSTREAM_PUSH_URL), set idempotently on every run so
existing cached clones self-repair.
2026-08-27 01:10:33 -04:00