From 063432aecd36ad1e57cbefb24e27ae787ec96cd8 Mon Sep 17 00:00:00 2001 From: Seth Bergman Date: Tue, 15 Sep 2026 22:07:41 -0500 Subject: [PATCH] Record what v0.19 shipped MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Three defects on the path between a running cluster and a configured one, all found by staging the first real AWS apply rather than by running it. The README bump is in the same commit because it has to be: the lint added in v0.19 requires the README's version claim to name the newest row of this table. That is the first time it has bound a release, and it binds it the right way round — the roadmap row is the source of truth, and the tag comes after both. Co-Authored-By: Claude Opus 5 --- README.md | 2 +- docs/roadmap.md | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2cb839e..3ec457f 100644 --- a/README.md +++ b/README.md @@ -441,7 +441,7 @@ See [`.github/workflows/ci.yml`](.github/workflows/ci.yml). ## Roadmap -Everything through v0.18 has shipped — see +Everything through v0.19 has shipped — see [Releases](https://github.com/sethbergman/vault-reference-platform/releases) for the log. "Shipped" here means there is a test that fails if the feature breaks, not that the code exists. diff --git a/docs/roadmap.md b/docs/roadmap.md index 57d3ca5..57feeb7 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -28,6 +28,7 @@ and which parts are a plausible-looking configuration nobody has run. | v0.16 | Audit anchors shipped to storage that refuses to delete them, on both clouds; key rotation and recovery rekey; a snapshot read back out of object storage and restored | | v0.17 | Seal migration in both directions, and the unseal-key rekey — plus the key the local root of trust had been discarding, which made restarting one container unrecoverable | | v0.18 | Rate limit quotas, and the three ways of setting one that write successfully and protect nothing — including the quota that refuses its own deletion | +| v0.19 | The path from a running cluster to a configured one, which had three breaks in it: three nodes arriving as one Ansible host, no way to reach any of them, and a certificate check no correct certificate could pass | ## The honest gap