amadan
README: release note for 7-day history on sleeping instances (#263)
Approved in copy review 2026-10-08, unedited. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Human
Prompt
Yes.
From this commit's own message. The prompt ledger has no entries for it — which is what a squashed, rebased or amended commit looks like, and what every commit looks like in a repo without a ledger.
Summary
Adds the operator release note for #263.
1 file changed,
+18
−0
README.md+18 −0
CI passed — run details
diff --git a/README.md b/README.md| index eee29768b..e2a7dcccf 100644 |
| --- a/README.md |
| +++ b/README.md |
| @@ -438,6 +438,24 @@ placements (#409). |
| release: only this release's DNS steering leaves replicas out of |
| latency routing. |
| +### Seven days of history for sleeping instances (2026-10-08) |
| + |
| +This release keeps seven days of database snapshots for instances that |
| +sleep, the same as instances that stay awake (#263). `carlos db pull --at` |
| +(#262) can then reach back a week on them, not a day. |
| + |
| +- boxes only. the console is unaffected. |
| +- the window fills in over the week after the roll. snapshots older than a |
| + day were already deleted under the old setting, so on the day of the roll a |
| + sleeping instance still reaches back about a day, and a week only seven |
| + days later. |
| +- an instance's history moves only while it is awake. one that sleeps for |
| + several days takes no snapshot in that time, and loses none either: |
| + retention also runs only while it is awake. |
| +- storage grows by up to six more daily snapshots per sleeping instance, |
| + plus the hourly files back to the oldest one. there are no extra s3 |
| + requests. |
| + |
| ## App config & secrets |
| Per-app config lives in the deployment bucket |