# Release v2.18.1 — the release keys built in

Released 2026-10-26 from `refactor` → `master`, tagged `v2.18.1`, on top of
v2.18.0 (`docs/release-v2.18.0.md`).

## The release agent's keys

gatewayd and `install.sh` now carry the release agent's two Ed25519 public
keys (also published in `README.md`, outside the site):

| Key | keyid | Public key (raw 32 bytes, base64) |
|---|---|---|
| primary — signs releases and the channel | `03ea7f6bcef4ab19` | `/2vPiKRblHb7DU5RieDfNjlZsqf/LN+JYqC/ilccSZA=` |
| reserve — revokes a key; signs only while a lost primary is replaced | `e740c848903fec85` | `gqUmZrBRpALaJOEXfUq3YTQ2KJ9j9IB01SbsKjtMySs=` |

- **The release cache** takes an archive or a site release signed by them as
  "signed"; one signed by no trusted key still comes in unsigned and waits
  for an admin to accept it.
- **The release site** (System → Updates): Check now and the notify / auto
  policies read `releases/channel.json`, verified against these keys; the
  channel's term and a revocation under the reserve key work from now on.
- **auto** can take a release now: signed by a built-in key, after the delay,
  in the maintenance window (still off unless chosen; a development build
  never uses it).
- **`install.sh`** refuses a release whose `SHA256SUMS` these keys did not
  sign; the releases before them install with `GATEWAY_ALLOW_UNSIGNED=1`.

## Fixed

- `BUILDINFO` was written with CRLF line ends when the release was built on
  Windows (v2.18.0's has them; it is still valid JSON). It is written as LF
  bytes now.

## Upgrading

- From v2.18.0: it trusts no key, so upload this release's archive by hand
  (System → Updates → Upload) and accept it, or run the installer.
- From v2.17.0: run the installer (`requires_installer`), as for v2.18.0.
