* 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
The release service stores each file at files/<sha256>/<name> and serves it as an attachment named <name>, so names need no version or target: linux-x64 is hex, macos-arm64-dmg Hex.dmg, macos-arm64 Hex.zip, windows-x64/arm64 hex.exe, and the Windows installers HexSetup.exe (the service's names allow no spaces). Targets reference {file, sha256}, so the two Windows architectures may share a name. Builds and the GitHub release mirror keep versioned names; release-service.sh maps them. The updater, installers, and AUR PKGBUILD (hex-<pkgver>-linux-x64::<url>) take the URL from the manifest; the AUR and Homebrew renderers accept the new URLs, and the cask URL no longer interpolates the version.
Build jobs (Linux, Windows x64/ARM64, macOS, Windows installers, AUR and Homebrew staging) run repository code with no environment, secret, or id-token and produce unsigned files. Sign and publish jobs run in the release environment, check out only .github/release/, and run only those scripts and SHA-pinned actions on artifacts treated as data: macOS Developer ID signing, notarization, and stapling (from APPLE_SIGNING_CERTIFICATE, APPLE_NOTARY_KEY, and the APPLE_NOTARY_KEY_ID/ISSUER_ID variables), Azure Authenticode, the release service, the GitHub release, and the AUR and Homebrew pushes. Every artifact carries a SHA256SUMS whose digest its job reports; every job that downloads it checks that digest. Signed macOS builds are verified and launched in a job without secrets. macos-signed.yml is gone (a check run covers it); the site deploy is no longer part of Release.
The updater refuses an update whose binary reports another version than the manifest, so staging stamps the prerelease into Cargo.toml and Cargo.lock before building; the AUR package spells it as pkgver X.Y.Z_dev.N.
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.