* 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
* 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.
* 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
* 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
* 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
hex-legacy-downloads now also takes hex.kitlangton.com and .dev (the old hex-voice-site website) as custom domains, 301 to anoma.ly/hex with /download and the installer paths mapped; the downloads hosts keep their 302 routes to anoma.ly/hex/files. README gives Kit the one deploy command, the fallback if wrangler refuses, and the rollback. Removes the accidentally committed .wrangler/ state and ignores it everywhere.
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.
* Drop glib/gio and tray-icon: Rune tray and file dialogs, zbus for the portal and MPRIS
* Drop glib from packaging, Nix, CI and docs; Rune tray and dialogs in the docs
* fmt; Nix hash for Rune 07520d0
* Drop Input Monitoring: Accessibility covers the shortcut taps (t496)
* Regenerate goldens without the Input Monitoring row (t496)
* Regenerate the permissions golden after merging dev (t496)
* macOS: lay out the installer window with Hex's keycap (t423)
The DMG opens on a light window with Hex, an arrow to Applications, and Hex's own dark Option keycap beside "Hold it, say it, done." packaging/macos/dmg holds the background (1x and 2x TIFF), Finder's .DS_Store, and render.sh, which draws the keycap with Rune and regenerates both. scripts/notarize-app.sh lays out the local DMG with them; the Release workflow's DMG follows in a separate .github/ PR.
* Show the whole background: the window height includes its title bar
* Follow the hex rename; satisfy clippy
* Rename voice-control to hex everywhere, without migrations
The Cargo package and binary are now hex, every OS keeps its data in a
hex folder, and VOICE_CONTROL_* variables are HEX_*. Hex is a fresh
app: the macOS voice-control rename, its symlink, and the Windows and
Linux beta settings imports are gone. The Windows installer gets a new
AppId so it never takes over an old voice-control install's entry.
* Format
* Drop the Windows paste-last default only the beta import used
* Linux ARM64, .deb, and .rpm releases
Both Linux architectures build natively on Ubuntu 24.04 runners (glibc 2.39
floor, Vulkan on both), publish linux-arm64 plus linux-<arch>-deb and -rpm
(hex.deb, hex.rpm) built with nfpm and installed on Ubuntu and Fedora in the
build job. hex-bin gains aarch64. Package installs report deb-<arch> or
rpm-<arch> through dpkg/rpm ownership and get the stable update command.
* build-linux.sh prints only the executable's path
* Linux releases link no system BLAS, as the Arch build shipped
* Linux build: keep libopenblas-dev for build.rs's dropped -lopenblas
Dev and check runs stamp 0.0.0-dev-$GITHUB_RUN_NUMBER with no tag lookup; versions are display text that the release service and the updater never compare, so builds numbered below 2.3.1 are fine. macOS dev builds take the run number as CFBundleVersion. The Linux and Windows installers and the Windows Setup.exe no longer refuse to install a lower version than the one installed. Docs describe following the channel's current release, required releases, rollbacks, and confirmed channel switches. Also drops an unused import that failed Check macOS.
A homebrew job renders anomalyco/tap/hex from the published DMG (anomaly.hex, auto_updates, release-service livecheck, zap paths), checks it with brew style and brew audit on a macOS runner, and on stable pushes it to anomalyco/homebrew-tap with the deploy key github-actions-hex-homebrew; record-brew then records the brew distribution. The manual cask step and the brew-version dispatch are gone.
CaptureTarget::Phone records the first cabled iPhone through scrawl-helper's
mirror with --no-microphone; the phone finish takes Hex's timeline audio
(moved onto the movie's clock) and Hex's transcriber instead of the movie's.
CaptureSnapshot.phone comes from a capture-phone look at each start and on
CaptureCommand::FindPhone. A mirror that ends on its own finishes its capture.
HEX_CAPTURE builds add NSCameraUsageDescription; validate-app refuses it.
cfg(hex_capture) is now a macOS build with the capture feature, debug or
release, so Kit can run captures in a release Hex. Builds without the
feature are unchanged: no experiment, scrawl-capture refused unsupported,
the crate not compiled. hex dev capture-replay stays debug-only.
HEX_CAPTURE=1 scripts/build-app.sh builds with the feature and signs
scrawl-helper into Contents/MacOS, where the engine looks for it, with
Hex's identity (embedded plist anomaly.hex.scrawl-helper), hardened
runtime, and no entitlements, before the app. release-app.sh refuses
HEX_CAPTURE, and validate-app.sh refuses a bundle with scrawl-helper or
the capture host in hex.
Hex polls anoma.ly/release/hex/desktop/<channel>.json on every OS and decides
with the release protocol's client rules (the service's shared test vectors in
tests/fixtures/release-protocol): strictly newer unless revoked, the minimum
version before rollout, and a device-local rollout bucket that is never sent.
Direct installs (Linux and Windows with the installer's receipt, macOS a
replaceable Hex.app) download resumably, check size and SHA-256, then the OS
code signature (macOS app/update-requirement.txt: Developer ID 5NZ4Q7NXJ4,
anomaly.hex, notarized; Windows Authenticode from Anomaly's Artifact Signing
identity), and stage the update for Restart to update. macOS swaps the bundle
in with renamex_np(RENAME_SWAP) at restart or quit; a read-only location links
to the DMG. Package-managed installs show their manager's command; source and
test builds never check; DisableUpdates (macOS defaults, Windows policy key)
turns checks off.
Sparkle, its framework, Info.plist keys, appcast generation, and the ed25519
feeds are gone. release-app.sh prepare leaves Hex-<v>-macos-arm64.dmg and .zip
(root Hex.app). Macs on 2.3.1 get packaging/macos/legacy-appcast.xml: one
informational item linking to anoma.ly/hex.
The Release workflow uploads each target and the release to anoma.ly/release (dev.anoma.ly/release for staging) with curl and its GitHub OIDC token, records the AUR, Homebrew, and Nix distributions, mirrors the files to GitHub, and builds hex-bin from the published file. The ed25519 feeds, appcast generation, and Sparkle ZIP naming are gone; the 2.3.1 feeds stay frozen. Builds and installers use the release service names, the installers read the stable manifest and write the direct-install receipt, and the site reads its download links from the manifest.
It is the Hex voice dictation app, not a prebuilt of extra/hex (a hex dump tool that installs /usr/bin/hx), so it neither provides nor conflicts with it, and its description says so.
A staging channel dry-runs the whole pipeline under staging/<run-id>/ with a draft GitHub release; uploads use the bucket-scoped R2 S3 credentials. Adds the hex-voice-bin AUR package and docs/releasing.md.
The Linux host, the single-instance socket, the HUD, and the window run in
one process. A relaunch forwards Activate with the launcher's activation
token; hex dictation, voice-action, paste-last, status, and quit forward
over the same socket, and shortcut commands go straight to the listener.
Without an instance a launch starts the managed unit (Type=notify) or
becomes Hex. The Rune window is the default on rune-ui builds and talks to
the host directly; GPUI stays behind --ui gpui. Quit Hex lives in the
sidebar.
* feat(windows): a per-user Setup.exe installer for the managed layout
* feat(release): build, test, and publish Setup.exe installers and the GitHub download mirror
* fix(onboarding): name the tray on Windows and the background service on Linux; keep Apps & Features on the updated version
* feat(site): one site with a platform-aware download section; retire hex.kitlangton.com
* feat(site): prerender the page, add robots, sitemap, llms.txt, JSON-LD, and favicon.ico