Commit Graph
5 Commits
Author SHA1 Message Date
ryanrhughes 0cda546059 Track upstream branches: basecamp-cli 0.13.0, brave-bin 1.97.56, brave-origin-bin 1.97.56, claude-code 2.1.295, claude-desktop 2.31226.0, cursor-bin 3.24.9, github-copilot-cli 1.0.94, lmstudio-bin 0.4.26, microsoft-edge-stable-bin 155.0.4283.45, mise-bin 2026.10.4, monologue 0.3.1, openai-codex-bin 0.162.0, openai-codex-desktop 26.1007.21434, openclaw 2026.9.9, slack-desktop 4.52.178, visual-studio-code-bin 1.141.0, zed 1.23.2, zen-browser-bin 1.23.1b 2026-10-09 15:31:54 +00:00
David Heinemeier HanssonandClaude Opus 5.5 88947c367b Auto-merge upstream updates for trusted packages (#892)
* Auto-merge upstream updates for trusted packages

The unattended lane already runs every upstream provider, not only branch
watches, so trusted release feeds can ship without waiting on the reviewed
sync PR. Opt in the browsers, large vendors' apps, Omacom's own projects,
and the vendor binaries that hold fresh releases for 24h: 39 packages,
including rawmakase-bin and gliff.

Drivers, firmware, the bootloader, core desktop components, beta and
nightly channels, and community projects stay on the reviewed lane.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Auto-merge grok-bot, perplexity, disktree-bin, cliamp, openclaw, voxtype-bin and ttfx

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 16:42:23 +02:00
David Heinemeier Hansson a1ad25bbae Bump releases for packages with mismatched cached archives (#858) 2026-10-08 15:01:06 +02:00
emirb 285d290199 chore: sync upstream releases 2026-10-04 01:23:03 +00:00
David Heinemeier HanssonandClaude Opus 5.5 1299a82d79 Package the browsers Omarchy installs from the AUR
omarchy-install-browser still reaches for yay to install Chrome, Edge,
Brave, Brave Origin and Zen. These were the only packages anywhere in
Omarchy's installers and menus that aren't available from core, extra,
multilib or OPR. Serving them from OPR means installing any Omarchy
browser no longer depends on the AUR being up.

Imported once from the AUR with bin/add-package, on the fast ring so
browser security releases reach stable promptly, each with a direct
vendor watch:

- google-chrome: Google's stable apt index
- microsoft-edge-stable-bin: Microsoft's stable apt index
- brave-bin, brave-origin-bin: Brave's stable apt index. Brave's
  GitHub releases can't be used because nightlies aren't marked as
  prereleases there.
- zen-browser-bin: GitHub releases (the twilight tag doesn't match)

Package names match what Omarchy's scripts already check for, so the
existing omarchy-pkg-aur-add calls resolve to the repo package without
any change on the Omarchy side.

Validation: upstream-watch check reports all five as current. A sync
of downgraded copies of zen-browser-bin and brave-origin-bin reproduces
the checked-in pkgver and both architectures' checksums. All five build
with makepkg on x86_64, and the launchers, desktop IDs and /opt paths
match what omarchy-default-browser and omarchy-theme-set-browser use.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-26 16:46:01 -04:00