<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Durable Runner changelog</title><description>What changed in Durable Runner, the open-source durable workflow runner: features, fixes, security fixes and breaking changes.</description><link>https://docs.durable-runner.404human.dev/</link><language>en-gb</language><item><title>Feature: v1.0.0: the first stable release</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-19-v1-0-0</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-19-v1-0-0</guid><pubDate>Thu, 19 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;The first stable release, and what a reader can now rely on. The core promise is unchanged: a
submit is acknowledged only after a durable commit, acknowledged runs survive &lt;code&gt;kill -9&lt;/code&gt; and
reboots, and the framed append-only journal — one writer, exclusive lock — is the only authority.
Journal records are now versioned: new records carry &lt;code&gt;v: 2&lt;/code&gt;, readers accept v1 forever and refuse
unknown future versions rather than guess, and &lt;code&gt;--journal-format&lt;/code&gt; plus &lt;code&gt;deploy/format-guard.sh&lt;/code&gt;
refuse an upgrade or rollback to a binary that can’t read the journal — failing closed, not eating
state.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Per-client limits ship.&lt;/strong&gt; One address gets 100 requests/s by default (&lt;code&gt;429 rate_limited&lt;/code&gt; with
&lt;code&gt;Retry-After&lt;/code&gt;), connection caps for untrusted peers and separately for trusted proxies, and
&lt;code&gt;--trusted-proxy&lt;/code&gt; CIDRs that decide whose &lt;code&gt;CF-Connecting-IP&lt;/code&gt; is believed — anyone can set that
header, so it’s believed from no one else. IPv6 keys at /64 with a /48 aggregate.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Capacity is measured, not assumed.&lt;/strong&gt; Two honest numbers: a 12-core laptop sustained 100
submits/s — 1,000,000/1,000,000 done, p99 41 ms — and a 4-core CI runner topped out near ~85
completions/s, so a 100/s offer had 835,397 accepted then refused the rest &lt;code&gt;503 at_capacity&lt;/code&gt; at
the 100,000-live-run bound. The CI miss is kept as evidence, not rerun until green: over-offered,
the server keeps completing at its own rate and refuses the overflow by name. Your own host gets
the same probe before traffic — see &lt;a href=&quot;https://docs.durable-runner.404human.dev/self-hosting/capacity/&quot;&gt;Capacity&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The Inspector covers everything now&lt;/strong&gt; — submit, list, detail, spec read-back, cancel,
diagnostics, compact, backup — with two-step confirms on mutations, keys in &lt;code&gt;sessionStorage&lt;/code&gt; only,
light/dark tokens and a phone layout that stays unclipped at 390 px. And a deploy kit ships with
the repo: hardened systemd unit, Caddyfile with &lt;code&gt;lb_try_duration 15s&lt;/code&gt;, Cloudflare ranges feeding
both trust boundaries, daily encrypted backups under a 7-day lock, and upgrade/rollback scripts
behind the format guard.&lt;/p&gt;
&lt;p&gt;Read more: &lt;a href=&quot;https://docs.durable-runner.404human.dev/self-hosting/capacity/&quot;&gt;Capacity&lt;/a&gt; · &lt;a href=&quot;https://docs.durable-runner.404human.dev/self-hosting/configuration/&quot;&gt;Configuration&lt;/a&gt; · &lt;a href=&quot;https://docs.durable-runner.404human.dev/inspector/&quot;&gt;The Inspector&lt;/a&gt;&lt;/p&gt;</content:encoded><category>Feature</category><category>API</category><category>CLI</category><category>Inspector</category><category>Journal</category><category>Server</category><category>Self-hosting</category></item><item><title>Feature: Handler calls say which run, step and attempt they are</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-17-handler-headers</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-17-handler-headers</guid><pubDate>Tue, 17 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Every call the runner makes to a step handler now carries &lt;code&gt;x-durable-run-id&lt;/code&gt;, &lt;code&gt;x-durable-step&lt;/code&gt; and
&lt;code&gt;x-durable-attempt&lt;/code&gt; alongside the input and the idempotency key, so a handler can log, trace or
reconcile an individual attempt without parsing the body. The reconciliation probe carries the same
headers.&lt;/p&gt;
</content:encoded><category>Feature</category><category>API</category></item><item><title>Improvement: One million submits in a single sustained run</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-17-million-submits</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-17-million-submits</guid><pubDate>Tue, 17 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;The load harness completed a sustained run of 1,000,000 acknowledged submits against a single
runner — every acknowledgment committed to the journal first — with the group’s batching and bounds
holding throughout. Result records no longer carry the machine’s hostname.&lt;/p&gt;
</content:encoded><category>Improvement</category><category>Performance</category><category>Journal</category></item><item><title>Feature: The API key reads back a run&apos;s submitted spec</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-17-spec-readback</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-17-spec-readback</guid><pubDate>Tue, 17 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;&lt;code&gt;GET /jobs/{id}/spec&lt;/code&gt; returns the spec exactly as it was submitted — the version, the steps and the
base64 input — so a controller can resubmit the same work under a new &lt;code&gt;op_key&lt;/code&gt;, or audit what a run
was asked to do. Because the input may be job content, the read-only key cannot use this route:
it answers &lt;code&gt;403&lt;/code&gt; to the read key and to open reads.&lt;/p&gt;
&lt;p&gt;Read more: &lt;a href=&quot;https://docs.durable-runner.404human.dev/api/reference/&quot;&gt;API reference&lt;/a&gt;&lt;/p&gt;</content:encoded><category>Feature</category><category>API</category></item><item><title>Fix: A backup whose file list is wrong is refused by name</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-16-backup-list-checks</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-16-backup-list-checks</guid><pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Restore and backup verification now reject a manifest that names the same file twice or lacks a
checksum for a file it lists — and the error names the file, so a damaged backup is diagnosable
instead of mysteriously unrestorable. The checks happen before a byte of the target is trusted.&lt;/p&gt;
&lt;p&gt;Read more: &lt;a href=&quot;https://docs.durable-runner.404human.dev/self-hosting/backups/&quot;&gt;Backups&lt;/a&gt;&lt;/p&gt;</content:encoded><category>Fix</category><category>Server</category></item><item><title>Fix: Job input must be canonical base64, refused with one stable message</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-16-canonical-base64</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-16-canonical-base64</guid><pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;&lt;code&gt;input_b64&lt;/code&gt; in a submit now has to be canonical, padded standard base64 (RFC 4648). Anything else —
unpadded, URL-safe alphabet, stray whitespace — comes back &lt;code&gt;400 bad_input&lt;/code&gt; with a single stable
message instead of the decoder’s own wording, which varied between versions.&lt;/p&gt;
</content:encoded><category>Fix</category><category>API</category></item><item><title>Security: Connections are capped, and every request is on a deadline</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-16-conn-limits</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-16-conn-limits</guid><pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;The server now bounds its connection count and enforces deadlines on request headers and bodies, so
a client that drips bytes or never reads its response can no longer hold a connection forever.
Bodies cut off at their deadline answer &lt;code&gt;408 body_timeout&lt;/code&gt; instead of a parse error.&lt;/p&gt;
</content:encoded><category>Security</category><category>Server</category></item><item><title>Fix: SIGTERM exits non-zero when the drain timeout cuts requests short</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-16-drain-exit</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-16-drain-exit</guid><pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;A clean stop is supposed to mean clean. The server now exits &lt;code&gt;0&lt;/code&gt; on SIGTERM only if it finished
within &lt;code&gt;--drain-timeout-secs&lt;/code&gt; — requests answered, decisions made durable. If the deadline cut
anything off, it exits non-zero, so systemd and operators can tell a drained stop from a forced
one instead of assuming both look the same.&lt;/p&gt;
&lt;p&gt;Read more: &lt;a href=&quot;https://docs.durable-runner.404human.dev/self-hosting/deployment/&quot;&gt;Deployment&lt;/a&gt;&lt;/p&gt;</content:encoded><category>Fix</category><category>Server</category></item><item><title>Improvement: The crash drill kills the server mid-work and loses nothing</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-16-kill9-drill</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-16-kill9-drill</guid><pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;The recovery drill now stops the server with &lt;code&gt;SIGKILL&lt;/code&gt; in the middle of real submits and
replays the journal afterwards: every acknowledged run came back, zero lost. Frame, snapshot and
index formats are pinned by golden files too, so an accidental format change fails a test instead
of reaching a journal.&lt;/p&gt;
&lt;p&gt;Read more: &lt;a href=&quot;https://docs.durable-runner.404human.dev/concepts/&quot;&gt;Concepts&lt;/a&gt;&lt;/p&gt;</content:encoded><category>Improvement</category><category>Journal</category></item><item><title>Security: Open reads answer only requests addressed to a loopback Host</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-16-open-reads-host-check</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-16-open-reads-host-check</guid><pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;&lt;code&gt;--open-reads&lt;/code&gt; was already refused at startup on a non-loopback listen. Now it also checks the
request’s &lt;code&gt;Host&lt;/code&gt; header against the listener, so a web page that rebinds an attacker-controlled
name to &lt;code&gt;127.0.0.1&lt;/code&gt; (DNS rebinding) can’t read the run list through the victim’s browser. It
changes nothing about the rule that matters most: never put &lt;code&gt;--open-reads&lt;/code&gt; behind a proxy.&lt;/p&gt;
&lt;p&gt;Read more: &lt;a href=&quot;https://docs.durable-runner.404human.dev/api/authentication/&quot;&gt;Authentication&lt;/a&gt;&lt;/p&gt;</content:encoded><category>Security</category><category>Server</category></item><item><title>Security: Reads need a key, and a read-only key exists</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-16-read-key</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-16-read-key</guid><pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Listing and inspecting runs now requires a key. Servers can set a second, read-only key that may
list and inspect but is refused (&lt;code&gt;403&lt;/code&gt;) on submits, cancels, admin routes and spec read-back. For
trusted local tooling, &lt;code&gt;--open-reads&lt;/code&gt; still opens the two read routes — but only for requests that
arrive on loopback addressed to a loopback Host, so a browser on the same machine cannot be talked
into reading through it. Never place &lt;code&gt;--open-reads&lt;/code&gt; behind a proxy.&lt;/p&gt;
&lt;p&gt;Read more: &lt;a href=&quot;https://docs.durable-runner.404human.dev/api/reference/&quot;&gt;API reference&lt;/a&gt;&lt;/p&gt;</content:encoded><category>Security</category><category>API</category><category>Server</category></item><item><title>Fix: Restore re-verifies each backup file as it writes it</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-16-restore-hardening</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-16-restore-hardening</guid><pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;&lt;code&gt;durable restore&lt;/code&gt; now re-checks each file after opening it — so it restores the bytes it verified,
not whatever landed in the meantime — and it fsyncs the target directory before publishing the
restored manifest. A backup list with a duplicate entry or a missing checksum is refused by name
instead of producing a partial restore.&lt;/p&gt;
</content:encoded><category>Fix</category><category>Journal</category></item><item><title>Feature: Earlier milestones</title><link>https://docs.durable-runner.404human.dev/changelog/#2026-11-15-earlier</link><guid isPermaLink="true">https://docs.durable-runner.404human.dev/changelog/#2026-11-15-earlier</guid><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Everything before this window, in one card: the framed append-only journal with one writer and an
exclusive lock; the engine that dispatches steps to allowlisted HTTP handlers at-least-once under a
single idempotency key and reconciles lost replies by probe; the nine-route HTTP API with its error
envelope; the operator CLI; consistent backups and verified restores; snapshots and compaction;
and the read-mostly Inspector served same-origin. The pages on this site cover each in depth —
start with &lt;a href=&quot;https://docs.durable-runner.404human.dev/concepts/&quot;&gt;Concepts&lt;/a&gt;.&lt;/p&gt;
</content:encoded><category>Feature</category><category>Journal</category><category>Server</category><category>API</category><category>CLI</category><category>Inspector</category></item></channel></rss>