* iOS: move Hex for iPhone to Anomaly's Apple team
(cherry picked from commit 09061502ff)
* Cut Hex Mobile TestFlight betas with a dedicated release tag
Connect the Anomaly app record and pin the mobile package graph. Cut ios-beta prereleases from dev at the scheduled windows or on dispatch, skipping unchanged mobile inputs instead of creating desktop releases or allocating build numbers locally. Prepare the generated project for the Cloud archive after clone.
Verified actionlint, duplicate and desktop-only skips, strict SwiftPM resolution, and an unsigned Release device archive containing the app, keyboard, and widgets. First Xcode Cloud onboarding and signed distribution are still pending.
---------
Co-authored-by: Kit Langton <kit.langton@gmail.com>
* windows: sign the setup engine so smart app control can run setup
Setup extracts a copy of its engine to %TEMP% at launch and writes the
installed uninstaller from the same bytes. Signing only the outer
hex-setup-*.exe left both unsigned, and Windows 11 Smart App Control
blocked the extracted copy ("Unable to execute file in the temporary
directory", error 4551).
SignedUninstaller embeds the engine's signature, but the signature has to
exist before the compile that uses it, and the compile job holds no
credentials. So the release signs it in two passes: the new
windows-setup-engine.yml compiles once with SignedUninstaller=yes and keeps
the unsigned uninst-*.e32 ISCC asks to be signed (ISCC leaves it and aborts
as a compile failure, exit 2); sign-windows-engine signs and verifies it in
the release environment; windows-installers.yml then compiles with the
signed engine and asserts the installed uninstaller's signature.
Test builds and runs without the Azure values keep the unsigned single
compile. Inno Setup is pinned to 6.7.1, read from the compiler's own banner
(ISCC.exe's version resource is 0.0.0), so both passes use one compiler.
* windows: harden the setup engine passes
Review fixes for the signed setup engine:
- sign-windows-engine requires sign-windows to have succeeded, and its
steps are unguarded like sign-windows-installers, so it can never upload
an empty digest.
- setup-engine runs only when Windows is signed (it waits for
sign-windows), so unsigned runs really do a single compile with no
engine pass at all.
- the Inno re-pin uses choco upgrade --allow-downgrade, because choco
install --version treats a preinstalled package as already installed.
- Invoke-Iscc collects native stderr safely under Windows PowerShell 5.1
and pwsh with $PSNativeCommandUseErrorActionPreference on, and echoes
the compiler's lines so build logs stay readable.
- the version probe compiles a minimal script from standard input into a
throwaway OutputDir, so it never touches the caller's -OutDir.
- only .e32 exists for the engine; drop the unused .e64 handling.
- the uninstaller signature test also checks the release publisher, and
the test-builds doc warns that Smart App Control cannot be turned back
on without resetting Windows.
* windows: correct the setup engine comments
github team caps us at 5 concurrent macos jobs, so macos jobs queue behind
each other. blacksmith has no concurrency cap and the same arm64 macos images.
converted: compile macos, check-macos test, release build-macos/verify-macos,
test-builds macos, release homebrew-stage.
sign-macos stays on github-hosted macos-26, like sign-windows: it holds the
release signing identity.
KDE's color-scheme portal describes window colors, so a mixed theme such
as Breeze Twilight picked a black mark for a dark panel. Bump rune for
TraySpec::icon_name, write anomaly.hex-symbolic.svg into the user's
hicolor theme at startup, and serve that name beside the pixmap so Plasma
6, GNOME's AppIndicator extension, and Waybar draw the mark in their own
text color. The icon keeps the old white/black default for hosts that
don't recolor, and the installer removes only a marked file.
Goldens follow the rune bump.
The site deploy job ran in the release environment and assumed role/github/hex-release, whose token could write every Worker on the account. It now runs in infra-dev or infra-production (picked from the mode, each admitting only its own branch) and assumes role/github/hex-infra-<mode>, which mints a token for that mode's Worker only. Release jobs stay in release.
The deploy job assumed role/github/hex-release and then read the long-lived
hex/release/CLOUDFLARE_API_TOKEN from Secrets Manager. It now mints a
15-minute token from the token issuer after assuming the role, masks it
before writing $GITHUB_OUTPUT, and passes it only to the Deploy step.
* ci: read release secrets from aws secrets manager
* ci: read the linux signing key from hex/release/RELEASE_SIGNING_KEY
* ci: hex's own aur and homebrew keys; the signing cert has no password
* ci: the signing certificate has no password
* ci: use the shared aur and homebrew keys
* docs: the shared homebrew deploy key is anomaly-release
* docs: the shared homebrew deploy key is anomaly-release
* site: own /hex/files, drop the r2 write credential (#1611)
* site: own /hex/files for installers, appcast, and dev notes
The site build now copies install-linux.sh, install-windows.ps1, and
packaging/macos/legacy-appcast.xml into its Worker assets, so the same
Worker serves them at /hex/files with the Content-Type and Cache-Control
the bucket objects had. The Installers and Legacy appcast workflows,
r2-put.sh, and their R2 write credential are gone.
The dev notes move to the one-commit dev-notes branch, published by
Release's dev-notes job with GITHUB_TOKEN only; the Worker proxies that
file at /hex/files/dev-notes.json (falling back to the bucket copy until
the first dev release creates the branch) and renders /hex/dev from it.
Both site Workers now bind hex-production-files, read-only in code, for
the frozen 2.3.1 feeds and artifacts, which lets hex-dev-files go. The
Site build runs the installer test and appcast check the removed
workflows ran, and the verify job compares the served bytes.
* docs: the site owns /hex/files and needs no R2 write credential
Hosting, secrets, old clients, and Linux packages describe the built
installers and appcast, the dev-notes branch, and the read-only bucket.
* fix(linux): name the missing wl-copy before a Wayland paste
* fix(linux): address review on wl-copy warning
* fix(settings): show the wl-copy notice apart from dictation failures
Stop a package stanza at the next table header, so a sourceless workspace
crate cannot borrow a following [[patch.unused]] Git source.
Assert the exact multi-crate problems instead of a string the script never
prints, and cover a sourceless package and a trailing patch table. Match the
test file in the compile path filter and the agent policy.
Read the resolved commit from the fragment, so branch, tag, short-rev, and
bare Git sources all work. Parse Cargo.lock's package stanzas with re so the
check runs on macOS's Python 3.9, reject lib.fakeHash, and normalize a .git
suffix when grouping repositories.
Add tests for each source form, a multi-crate repository, a stale revision,
and a fake hash. Flag the pin check itself in the agent policy.
The Rune 7d3ee6ca bump updated the Nix pin but not its output hash, so
nix build failed with a fixed-output mismatch.
cargoGitDependencies now records each Git dependency's revision beside its
output hash, and scripts/check-nix-git-pins.py fails when Cargo.lock names a
different revision. compile.yml runs it for Cargo.lock and nix changes.
Fixes#1397.
* Windows: ship hex.com, a console entry point beside the GUI hex.exe, on PATH
* lock, fmt, legacy adoption
* clippy
* build hex-console in its own cargo run: -p hex is ambiguous with the hex crate
* hex.com returns once the app starts; Ctrl+C only; install script and Setup replace a running hex.com; hex-console checks in Compile
* fmt
* installer test: exit 0 once every check passed
hex.exe is now a GUI program. Commands run from a terminal join it
(AttachConsole) and print there; the app leaves it after startup errors
have had their chance to print. Rune 31dbcad cloaks a window until its
first frame presents. Release checks assert the GUI subsystem.
* windows: delay-load vulkan-1.dll and fall back to CPU without a Vulkan 1.2 driver (#1240)
* windows: note vulkan-1.dll is delay-loaded in restrict_dll_search
* Onboarding gates stable releases: scene goldens and a clean first run (scripts/check-onboarding.sh), wired into Release
* Onboarding check: hero drawn, mic scenes, no false passes, locale pinned, dispatchable Check macOS
* Onboarding goldens: dark found scenes after #865
* Onboarding walkthrough: say what the fixture window doesn't do
* Linux: use the Background portal for running in the background and Launch at login (#812); fallback entry written once (#810)
* test names
* Docs: Background portal and Launch at login (#812)
* Background portal: only once registered (1.20+), symlinked entries are the user's, serialize entry writes and login changes
* doc comment
* Dev builds say what's new: notes from PR titles in the dev feed, /hex/dev, and Restart to update (#763)
* Dev notes: keep ReadyToRestart's wire format; canonical upload; script and refetch fixes from review
* Sidebar update in its own module (code-shape)
* x86_64: keep ggml on x86-64-v3 and refuse older CPUs with a clear message (#592)
Reverts #595's Ivy Bridge floor: it slowed CPU transcription for everyone. ggml goes back to its x86-64-v3 defaults (AVX2, BMI2, FMA, F16C). Hex's own Rust stays baseline x86-64, and the first thing main does on Linux and Windows x86_64 is check AVX2/BMI2/FMA/F16C with is_x86_feature_detected!. Without them Hex prints and shows "Hex needs a 2013 or newer processor (Intel Haswell / AMD Excavator or later) with AVX2. This PC's processor isn't supported." (a native MessageBox on Windows; stderr, which the journal logs, and zenity, kdialog or notify-send on Linux) and exits 1. Every command is covered except --version and --help, which installers and the updater run. ggml-cpu has no static constructors, so nothing runs v3 code before main.
The release guard now asserts the opposite: ggml's CPU libraries must hold AVX2 and FMA (the build targets v3) and no AVX-512 or AMX. Docs state the requirement.
* cpu_floor: harden DLL search first; no dialog under systemd, in a terminal or for hex service; guard rejects AVX-VNNI
* cpu_floor: always exit 1; Windows always shows the message box; Linux skips the dialog in a terminal, under NOTIFY_SOCKET, or for hex service
* Lowercase release file names; README downloads by channel (#456)
Release builds and the GitHub release mirror now name files hex-<version>-macos-arm64.{zip,dmg}, hex-<version>-windows-<arch>.exe and hex-setup-<version>-windows-<arch>.exe (Linux was already lowercase), as @vixalien asked in #456. Already-published files and the frozen 2.3.1 feeds keep their names; the release service's published names (hex, Hex.dmg, Hex.zip, hex.exe, HexSetup.exe) and the bundle (Hex.app) are unchanged, so the updater, installers, Homebrew cask, AUR and Nix are unaffected.
The README downloads table has Stable and Dev columns for every target, including the updater files. The site Worker serves /hex/download/dev/<target> (the dev alias) beside /hex/download/<target> (stable, or dev while there is none), and both now cover the bare updater files.
* Lowercase names in two remaining examples
* Lowercase the Windows executable in the CPU check step
* x86_64 releases: build ggml for the Ivy Bridge floor and fail on BMI2/AVX2/FMA (issue #592)
GGML_NATIVE=OFF alone leaves ggml's GGML_AVX2/BMI2/FMA/F16C on, so Hex 3.0.0 on Windows x64 died with 0xc000001d (illegal instruction) on an Ivy Bridge Xeon E3-1220 V2 once transcription started (reported by @Hc-Web-Dev). Linux and Windows x86_64 release builds now pin SSE4.2 + AVX + F16C and turn AVX2, BMI2, FMA, AVX-VNNI, AVX-512 and AMX off (scripts/ggml-x86-baseline.txt), the floor transcribe.cpp already uses on Intel Macs. Runtime dispatch (GGML_BACKEND_DL + GGML_CPU_ALL_VARIANTS) needs shared ggml libraries, which our single static executable can't ship. CPU transcription on newer x86 CPUs loses AVX2/FMA kernels; Vulkan is unaffected.
.github/release/check-x86-baseline.sh guards both build jobs: the executable may hold no BMI2 instruction (3.0.0's Linux build holds 100; Rust crates that use AVX2/FMA/AVX-512 behind run-time detection use none), and the ggml static libraries no AVX2, BMI2, FMA or AVX-512. No crate sets target-cpu; the only rustflags are +crt-static; no other C/C++ dependency builds with -march=native or AVX2 (Moonshine/ONNX are gone).
* check-x86-baseline: fail on missing inputs or empty disassembly; match llvm-objdump's suffixed BMI2 mnemonics
Homebrew 6 refuses to load casks from untrusted third-party taps, so the Hex 3.0.0 release's Homebrew check failed. The secretless check job now trusts our own tap after rendering the cask, guarded for Homebrew versions without brew trust. Second review: console-google/gemini-4-carbon-eap approved (session ses_e7096ffdfffeiCEi7ni1qQSPeP).
#424 removed Moonshine (and #430 Smart Turn's onnxruntime), but sign-macos.sh still required libmoonshine.dylib, so every Release since 0.0.0-dev-249 failed at sign-macos and nothing published. The bundle's code allowlist now requires only hex, scrawl-helper, and the microphone driver, and accepts libonnxruntime only if a build still bundles it. On the dev channel, publish no longer waits on macOS: when signing or verification fails, Linux and Windows still publish (only a verified macOS build is ever included), and the run still fails visibly. Stable still requires every platform.
site.yml runs on pushes to dev and production (site/ and the installers it copies) and derives the mode from the ref: production -> production, dev -> dev; dispatch follows the ref too, with no mode input. site-deploy.yml refuses a deploy whose mode doesn't match its branch.
Deterministic gate for agent/* pull requests: Dax-only paths always fail, flagged patches need the pipeline's strict reviewer. The script lives under .github so changing it needs Dax.
From the 2026-10-29 security review:
- H1: Release signs each Linux executable with Anomaly's ed25519 key (HEX_RELEASE_SIGNING_KEY, .github/release/sign-linux.sh, which refuses a key that does not match linux-signing.pub) and publishes the signature as the linux-<arch>-sig target. The updater (updater/linux.rs SIGNING_KEY) and install-linux.sh refuse an executable without a valid signature over its SHA-256, before downloading it. Installed builds that predate this ignore the extra target, so the transition needs nothing from them.
- H3: the installers move to the locked .github/release/ (CODEOWNERS @thdxr); the Installers workflow publishes them from a sparse checkout of that directory.
- M1: the release service client is vendored as .github/release/release-client.sh instead of piping anoma.ly/release/client.sh into bash.
- M2: check-windows.yml gets permissions: contents: read; every third-party action is pinned by SHA.
- M3: resolve_url accepts only URLs on the manifest's host.
build-macos ships the background TIFF and Finder's .DS_Store beside Hex.app.zip; sign-macos.sh checks both by magic number and size and copies them into the DMG as data.
* Captures on Linux: portal, PipeWire and VA-API behind the engine's platform seam; capture compiled into macOS and Linux builds
The capture engine's OS adapter gains capture/linux.rs: the screen-cast
portal (zbus) picks the screen (remembered with its restore token) or a
window, libpipewire and libva are loaded at run time, frames are imported
as DMA-BUFs and scaled and H.264-encoded on the GPU, and ffmpeg muxes and
reads movies back. Software x264 is the fallback.
capture_host, the capsule, the pane, routing and the CLI are shared; the
Linux listener feeds a ListenerTimeline, its portal or X11 grabs bind the
capture shortcut, and the summary goes through Hex's Linux clipboard.
The capture feature flag is gone: macOS and Linux always compile the
experiment, off by default.
* Docs: captures on Linux, the experiment in every macOS and Linux build; token path from Hex
* Capture portal: register Hex's app id so the desktop keeps its screen choice
* Fix macOS test build after the capture seam
* Linux: size X11 shortcut state for the capture shortcut; keep macOS-layout capsule tests on macOS
* Windows: the capture word timestamps field is Linux's
curl's own --retry reused the request's token, so a retry after a slow or
stalled upload could still hit 401 token expired. Retries now happen in the
script (up to 4 attempts on a failed transfer or a 429/5xx, each logged),
every attempt mints its own token, and a transfer stalled below 1 KB/s for a
minute is abandoned and retried. Multipart part PUTs and the finalize POST go
through the same path. Ports anomalyco/hokum 86d5ce3.