What iii-hq/iii shipped

0.26 work landed this week: sandbox routes to a configurable adapter, VM runs are explicit via sandbox run, and Observer capture decides when an observer fires. Windows Compose fixes, engine version ranges in worker config, standby removed from all five SDKs.

Several 0.26 changes landed this week. The built-in sandbox is now a router to a configurable adapter, and VM execution is explicit: compose no longer assumes a worker runs in a VM, and a new sandbox run command drives one container. Observe v2 moved forward, with capture deciding when an observer fires and what it receives, faster delivery with less memory per event, standby removed from all five SDKs, and parity fixes for OBSERVER_NOT_ACTIVE. Workers can declare an engine version range in iii.worker.yaml, which compose enforces. The engine now gives clear failures for removed trigger builtins, Windows Compose startup and log rotation were fixed, and a bench command compares a pull request against released versions.

Iii 0.26.0-rc.1 is out. Go SDK now at parity with Node, Python and Rust, with an API reference. New iii-sandbox-contract crate. Engine fixes for trigger teardown races and channel writer aborts. Compose stack now connects to Redis.

This week we published iii 0.26.0-rc.1 and released the Go SDK at parity with the Node, Python and Rust SDKs, with a new API reference. A new iii-sandbox-contract crate defines the wire contract between the engine sandbox router and sandbox adapters. On the engine side, trigger teardown races and cancellation are handled so provider jobs are not left active, and channel readers now get an error when the writer aborts. The Rust SDK keeps Logger lines under concurrency, Go workers keep websocket connections alive with pings and reconnect backoff reset, and the Docker Compose stack now reaches Redis with configurable bind host and URL. The Go SDK also moved to 0.26.0-rc.1.

Iii 0.25.0 is out: observers, messages up to 64 MiB, and the stream and pubsub deprecation. Oversized worker messages now keep the connection and return payload_too_large. Compose also extracts ZIP worker packages.

Iii 0.25.0 is released. The release brings observers to every function, raises the message limit to 64 MiB, and marks stream and pubsub as deprecated. A worker that sends an oversized message now keeps its connection and gets payload_too_large instead of being dropped, and the Rust, Node, Python and Go SDKs fragment envelopes between 16 and 64 MiB. Compose now extracts ZIP worker packages as well as gzip tar archives, fixing installation of Windows worker artifacts. The changelog for the release was also completed.

This week: III_TOKEN authenticates worker handshakes and channels, workers declaring an out-of-scope namespace are now rejected, configuration calls resolve in default, and TCP_NODELAY is set between engine and Rust workers. Plus deadlock and allocation fixes across engine, SDK a

Several fixes landed this week in iii. Workers can now authenticate to an RBAC listener with III_TOKEN instead of putting the session token in the URL. The engine rejects a worker that declares a namespace outside its session scope rather than quietly serving from default, and configuration calls resolve in default across SDKs while Go workers inherit their worker namespace. Networking and runtime work: TCP_NODELAY is negotiated between engine and Rust workers, WebSocket buffers held by queued HTTP bodies are released, and lock-order deadlocks in stream trigger cleanup and metric storage are fixed. Observability now enforces trace sampling and keeps archive writes bounded, and Python schema generation handles bare dict and list annotations.

New iii.dev is live with a landing page, manifesto, roadmap and blog. Also this week: engine functions-available updates now come from the registry with no polling task, sandboxes boot on a per-sandbox read-only overlay, and oversized JSON is rejected safely across the Rust, Node

The new iii.dev is live: landing page, manifesto, roadmap with spec pages, blog with RSS, privacy policy, and analytics that load only after consent. Alongside that, several changes landed in the project. The engine now drives functions-available updates from the registry itself, removing the background task that polled the registry hash every 5 seconds. Sandboxes boot on a per-sandbox read-only overlay instead of the shared image cache. Oversized JSON is rejected safely, with a 16 MiB serialized envelope limit in the Rust, Node, Python and Go SDKs. Compose shows per-worker update progress and running versions, and the installer now asks one setup question and skips setup when iii is already installed.

0.24.4 ships faster trace listings, optional span events/links, and Go trigger schemas. Engine reduces KV allocations and improves dependency planning.

Iii 0.24.4 is out. Trace listings now page over root keys instead of decoding every payload. Filtered traces reject candidates before decoding, using root keys and attribute indexes. Go trigger providers advertise schemas. The musl build installs glibc-only workers on glibc hosts. Python SDK reconnects after normal WebSocket closes. Compose plans batches efficiently with shared dependencies.

Iii 0.24.3 ships compose project reporting for startup visibility, fixes file descriptor exhaustion in long-lived connections, and removes the Amplitude vendor dependency.

Iii 0.24.3 is out. Compose now reports what projects do—critical for seeing startup failures and performance. Fixed channel socket leaks that exhausted file descriptors under load. Removed Amplitude telemetry to cut duplicate vendor calls and simplify the binary. Engine lifetime now follows compose process lifetime, with SIGHUP graceful shutdown.

Iii 0.25.0 week: non-interactive installs, worker scaffolding flags, concurrent package resolution, startup cancellation, Alpine musl support, and security updates.

This week's iii updates focus on installation flexibility and startup reliability. The installer now supports non-interactive mode and new scaffolding flags for declaring workers and requesting environment variables. Compose improvements include concurrent package metadata resolution, visible download progress, and the ability to cancel startup with Ctrl+C. Alpine musl workers are now supported with native artifacts, and dependencies have been updated for security and compatibility.