* 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.
The site's download buttons and the README/docs links name /hex/download/<target>, which the site Worker redirects per request to the release service's stable alias once stable.json exists and to the dev alias until then, so nothing needs switching back. The page labels the build ("Dev build 0.0.0-dev-N", with a note that it updates from the Dev channel) and refreshes the version from the live manifests. The Linux button names the site's own install-linux.sh. The anomalyco/homebrew-tap cask now installs the dev alias (version :latest, sha256 :no_check, auto_updates); the Release workflow's stable Homebrew job replaces it with a versioned cask at the first stable release.
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.
Release no longer runs on tag pushes; stable is a dispatch from production only and refuses a version already tagged v<version> or app-v<version>. After every platform and the release service published, a tag job pushes v<version> on the released commit with the release deploy key (HEX_RELEASE_TAG_KEY, admitted by the new v* tag ruleset), then the GitHub release mirrors the files on that tag; a failed run leaves no tag. A check run pushes and deletes a throwaway v0.0.0-test-<run> tag to prove the ruleset admits the key. The release environment now admits only dev and production.
dev.anoma.ly/release only tests the release service itself. The staging channel is gone: channel=check builds, signs, and verifies without publishing, and builds are tested before stable on anoma.ly/release's dev channel. The site (both environments), the Windows installer test, and the publish script read only anoma.ly/release. The installers take HEX_INSTALL_CHANNEL=dev to install the newest dev build onto the Dev update channel.
The release service now writes root-relative target URLs (/release/<app>/files/<sha256>/<name>); the publish check, the AUR source, the installers, the Windows installer test, and the site resolve them against the manifest's URL. A dev site without a platform's build links its frozen 2.3.1 download.
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.