flybrain/infra/docs/release-v0.1.3.md
acamilo 660c3cf00d
Some checks failed
ci / node 22 (test + typecheck) (push) Has been cancelled
ci / rust stable (cargo test --workspace --release) (push) Has been cancelled
ci / infra/tests/lint.sh (push) Has been cancelled
ci / playwright apps/stage (allowed to fail) (push) Has been cancelled
flybrain v0.4.0: public tree (history retained privately)
2026-09-21 15:09:46 +00:00

16 lines
867 B
Markdown

# Release v0.1.3 — method
> **The record lives in the operator's infra repo** (`services/flybrain/release-v0.1.3.md`), verbatim and dated: the tag, the
> commit, the box, the timings, the journal excerpts and the post-deploy checks.
The procedure this run followed is `infra/docs/runbook.md`'s "Cutting a release". Nothing
about the method is specific to this release; what is specific is the artifact and the
numbers, and those moved.
The two habits these runs put into the runbook:
- **Two `fly_lag_seconds` samples, one either side of the single `05-deploy.sh` call,
before any restart.** The metric only grows, so a single reading after a change says
nothing about the change.
- A release container takes **one** `05-deploy.sh` call and then the minimum restart:
restarting units that did not change is how a deploy drops a live stream for no reason.