carlos / platform Public

Adds the operator note for v0.22.0 to the README's release-notes section, as step 5 of "Releasing the platform" asks.

The public release notes for the GitHub release (the --notes-file in step 6) are below. Reviews: a Sonnet fact-check and copy review, then a Fable review (approve-with-amendments, all applied). The Fable review corrected the quoted old-console message and narrowed the long-poll claim to headers. It also added the replica flags being ignored by an old console, the Errors tab losing platform lines, console rollback safety, and #409's additive columns.

---

carlos v0.22.0 (platform 38639c1e, 2026-09-24)

• Availability: why a request got no answer. Every 502, 503 and 504 now records why: for example "the instance refused the connection", "the instance closed the connection mid-request", "no box of the fleet is connected", "the visitor gave up waiting for the instance", or "the app answered it itself". They sit on a new Availability tab beside Errors, grouped by cause instead of by page, so one outage is one row however many pages it hit. Failed wakes and exits are listed beside them. carlos availability --app <app> shows the same from a terminal, and --fp <id> lists one cause's occurrences with the page each was loading. Errors keeps the app's own 500s and log lines; failed wakes and exits have moved from Errors to Availability.
• Errors, Logs and Availability read chunks in parallel. Reading a day of log chunks used to mean one request after another. The console now fetches up to 16 at once and assembles them in the same order as before.
• Replica placements. carlos instances create --role replica --region <region> creates a second instance of an app in another region, holding a one-way mirror of the home instance's data. --replicas <regions> on the home instance publishes which regions serve the account; each replica is still its own create. A replica never receives latency-steered traffic: DNS latency routing keeps pointing buyers at the home instance.

Before you roll

• Roll the boxes and the console together. The boxes record causes and the console shows them. 502s already stored regroup under "cause not recorded", and rolling the console back is safe.
• A visitor who waits five seconds or more for response headers and then leaves is now filed as an outage. An endpoint that holds its headers longer than that by design, such as a long poll, will show a standing "the visitor gave up waiting for the instance" row. A visitor who leaves sooner is no longer filed at all.
• Update the console before using the new commands. Against an older console, carlos availability fails with not found: check --account and --app…, and carlos instances create --role replica is ignored: the old console creates an ordinary instance instead.
• Don't create a replica until every box runs this release. Only this release keeps replicas out of DNS latency routing.

Verify a download against SHA256SUMS.txt; SHA256SUMS.txt.sig is the ed25519 signature (base64) over that file, checked by carlos update against its embedded key.

---

First opened as github.com/carlosframework/platform/pull/421; moved to amadan when amadan became the source of truth (2026-09-24).