From 0f0cdbbb7f1356affb3876ff19d3c1250446dab0 Mon Sep 17 00:00:00 2001 From: Musa Musa Date: Sat, 29 Aug 2026 20:35:51 +0100 Subject: [PATCH] docs: record v0.6, and stop listing shipped work as upcoming MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 0.6.0 published two days ago and neither the README nor the roadmap page mentions it, so the docs describe a library one version behind the one on npm. Worse than the omission, the README's "still ahead" line listed adaptive throttling, execution budgets, hedging, criticality and per-tenant fairness — all of which appear as SHIPPED two lines above it, in v0.4 and v0.5. A reader comparing the two lists finds the page contradicting itself, which undermines every other claim on it. The roadmap page had the same problem in reverse: resilix/undici sat under "Ahead" while being the entire content of 0.6.0. Both now say what is true: v0.6 shipped resilix/undici, and what remains is resilix/nest, resilix/hono and inbound protection. --- README.md | 5 +++-- docs/guide/roadmap.md | 6 ++++-- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 6e3226e..7ecb9a9 100644 --- a/README.md +++ b/README.md @@ -369,9 +369,10 @@ Pre-release. built to [`docs/specs/adaptive-limiter.md`](docs/specs/adaptive-limiter.md) - **v0.4** retry with full jitter · shared retry budgets · SRE adaptive throttler · token-bucket rate limiter - **v0.5** hedging with cancellation · criticality buckets · tenant fairness +- **v0.6** `resilix/undici` — guard the dispatcher, and every call site in the process is covered -What is still ahead — adaptive throttling, execution budgets, hedging, criticality and -per-tenant fairness, then inbound protection — is in [`docs/public/resilix-architecture.pdf`](docs/public/resilix-architecture.pdf), along with +What is still ahead — `resilix/nest` and `resilix/hono`, then inbound protection: shedding load +you *receive* rather than load you send — is in [`docs/public/resilix-architecture.pdf`](docs/public/resilix-architecture.pdf), along with the C4 architecture and the reasoning behind every default. diff --git a/docs/guide/roadmap.md b/docs/guide/roadmap.md index bd9474a..25bc87a 100644 --- a/docs/guide/roadmap.md +++ b/docs/guide/roadmap.md @@ -12,6 +12,7 @@ lands with a changeset and a version bump. | **v0.3** | adaptive concurrency limiting · P² streaming quantiles · proportional shedding | | **v0.4** | retry with full jitter · shared retry budgets · SRE adaptive throttler · token-bucket rate limiter | | **v0.5** | hedging with cancellation · criticality buckets · tenant fairness | +| **v0.6** | `resilix/undici` — guard the dispatcher and every call site is covered at once | Each of v0.3–v0.5 was built to a spec written first — [adaptive limiter](../specs/adaptive-limiter), @@ -20,8 +21,9 @@ Each of v0.3–v0.5 was built to a spec written first — ## Ahead -- **More adapters.** `resilix/undici`, `resilix/nest`, `resilix/hono` — the same policies behind - the interface each ecosystem already uses, on the same optional-peer model as `resilix/otel`. +- **More adapters.** `resilix/nest` and `resilix/hono` — the same policies behind the interface + each ecosystem already uses, on the same optional-peer model as `resilix/otel` and + [`resilix/undici`](./undici). - **Inbound protection.** Everything so far guards calls you *make*. The symmetric problem — shedding load you *receive*, before it reaches your handlers — reuses the limiter and the criticality buckets but needs a different integration surface.