* 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.
* 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)