What iii-hq/iii shipped
Written by FoxPlug from the repository's own releases; not affiliated with Iii. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/iii-hq/iii; Iii did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of October 5, 2026
What shipped
- The new iii.dev site went live with a landing page, manifesto, roadmap with spec pages, blog with RSS, privacy policy, and a cookie banner that loads analytics only after consent. Pull request #2285
- The engine now drives the functions-available updates from the registry itself and the background polling task that checked the function registry hash every 5 seconds was removed. Pull request #2283
- Sandboxes now boot on a per-sandbox read-only overlay instead of the shared image cache. Pull request #2275
- Oversized JSON is now rejected safely: a 16 MiB serialized envelope limit is enforced in Rust, Node, Python, and Go, correlated
payload_too_largeerrors are returned without disconnecting, and SDK reception is bounded at 64 MiB. Pull request #2265 - Host-side file operations on an extracted OCI rootfs no longer follow symlinks or other non-regular entries that come from image layers. Pull request #2273
- Trace query snapshot allocations were reduced by projecting root-key metadata and trace tags without deep-cloning complete hot stored span payloads. Pull request #2286
- The Compose panel now shows per-worker update progress, the running version beside each worker, and the iii version beside a managed engine. Pull request #2263
- The installer now asks a single setup question, runs the first project init when you press Enter, and skips the setup prompt when iii is already installed. Pull request #2280
- Compose now ignores
env_filevalues that parse as empty while preserving quoted whitespace and explicit Compose behavior. Pull request #2274 - Version 0.24.4-alpha.3 was released for the engine, Node.js, Python, the browser SDK, and helpers. Release
Why it matters
This week the project gained a public site with a landing page, manifesto, roadmap and blog, so people can read about it and follow along. The engine, SDKs, sandboxing and Compose all changed too: functions-available updates come from the registry instead of polling, oversized JSON is rejected cleanly, and sandboxes no longer boot on the shared image cache. Installer and Compose reporting were simplified so setup and update checks are easier.
Changelog entry
- Release: iii 0.24.4-alpha.3 Release
- Release: sdk/packages/go/iii/v0.24.4-alpha.2 Release
- Release: sdk/packages/go/iii/v0.24.4-alpha.3 Release
- Release: sdk/packages/go/iii/v0.24.5-rc.2 Release
- Release: iii 0.24.6-rc.2 Release
- Release: sdk/packages/go/iii/v0.24.6-rc.2 Release
- Release: iii 0.24.6-rc.3 Release
- Release: sdk/packages/go/iii/v0.24.6-rc.3 Release
- Feat(website): new iii.dev live with landing, manifesto, roadmap, blog, privacy policy and consent-gated analytics Pull request #2285
- Fix(engine): drive functions-available from the registry and remove the polling background task Pull request #2283
- Fix(sandbox): boot sandboxes on a per-sandbox read-only overlay instead of the shared image cache Pull request #2275
- Fix(sdk): enforce a 16 MiB JSON envelope limit and return
payload_too_largeerrors Pull request #2265
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.
Week of September 28, 2026
What shipped
- Engine::traces::list no longer decodes every stored root payload, instead paging over root keys to improve listing performance. Pull request #2256
- Filtered engine::traces::list now rejects traces before decoding by using root keys and the attribute index. Pull request #2258
- Engine::traces::spans accepts
include_events: false to omit span events and links from responses. Pull request #2259 - Go custom trigger providers can now advertise configuration and callback payload schemas through RegisterTriggerTypeOptions. Pull request #2268
- Compose::update now plans the whole batch with the shared dependency planner instead of expanding each root independently. Pull request #2249
- Engine reduces avoidable builtin KV allocations and decouples heap maintenance from the observability worker lifecycle. Pull request #2261
- Observability span hot cache now releases the full allocation when truncating attribute values. Pull request #2264
- Website replaced the Astro site with a Next.js 16 rebuild of iii.dev using React 19 and Tailwind v4. Pull request #2239
- The musl build can now install glibc-only workers on a glibc host by resolving for the actual system triple. Pull request #2250
- Python SDK now reconnects after any WebSocket close including normal ones, fixing several connection states. Pull request #2243
Why it matters
This week focused on performance improvements for trace listing and filtering, with changes that avoid unnecessary decoding and allocations. The Go SDK gained schema advertising for custom triggers, and the compose system now plans dependencies more efficiently. These changes make the engine faster and more resource-efficient.
Changelog entry
- Faster trace listings: engine::traces::list pages over root keys instead of decoding every payload Pull request #2256
- Faster trace filtering: engine::traces::list rejects traces before decoding using root keys and attribute index Pull request #2258
- Engine::traces::spans accepts
include_events: false to omit span events and links Pull request #2259 - Go SDK: custom trigger providers can advertise configuration and callback payload schemas Pull request #2268
- Compose::update plans batches with shared dependency planner for better conflict handling Pull request #2249
- Engine reduces avoidable KV allocations and decouples heap maintenance from observability worker Pull request #2261
- Observability: span hot cache releases full allocation when truncating attribute values Pull request #2264
- Website rebuilt with Next.js 16, React 19, and Tailwind v4 Pull request #2239
- Musl build can install glibc-only workers on glibc hosts Pull request #2250
- Python SDK reconnects after normal WebSocket closes Pull request #2243
- Rust SDK updated async-trait for Rust 1.99 compatibility Pull request #2266
- CI runs Harness E2E suite on each published release Pull request #2253
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.
Week of September 21, 2026
What shipped
- Released iii 0.24.3 with compose project reporting, Amplitude telemetry removal, and channel socket fixes. Release
- Compose now reports what a project did, making startup failures and performance visible through events. Pull request #2221
- Fixed engine file descriptor exhaustion by releasing channel sockets as soon as either side leaves. Pull request #2230
- Runtime config overrides now reach workers through the configuration service without persisting to disk. Pull request #2231
- Managed engine lifetime now follows the compose process, with SIGHUP treated as graceful shutdown. Pull request #2227
- Engine telemetry now reports harness usage, long session flags, and collects operator email. Pull request #2213
- Website updated with compose::add examples, new onboarding script, and aligned AGENTS documentation. Pull request #2229
- Removed Amplitude vendor dependency, eliminating duplicate HTTP requests and API keys. Pull request #2222
- Configuration migration now uses exact default IDs and keeps overrides runtime-only. Pull request #2220
- Release workflow now accepts validated explicit version overrides for maintenance releases. Pull request #2218
Why it matters
Version 0.24.3 addresses critical resource leaks in the engine and improves visibility into compose startup behavior. The compose reporting feature makes failures and performance measurable for new users, while socket and telemetry fixes reduce infrastructure costs and operational complexity.
Changelog entry
- Feat(compose): report what a compose project did Release
- Chore(telemetry): remove Amplitude Pull request #2222
- Fix(engine): release channel sockets as soon as a side leaves Pull request #2230
- Fix(compose): deliver runtime overrides through the configuration service Pull request #2231
- Fix(compose): tie managed engine lifetime to compose Pull request #2227
- Feat(telemetry): report harness usage, flag long sessions, and accept email Pull request #2213
- Fix(compose): migrate readable config names and keep overrides runtime-only Pull request #2220
- Feat(release): allow validated explicit version overrides Pull request #2218
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.
Week of September 14, 2026
What shipped
- The installer now accepts --non-interactive flag or III_NON_INTERACTIVE environment variable to skip setup prompts. Pull request #2211
- Setup offers new flags: --start-with to scaffold and declare workers, --need-envs to request environment variables, and --skip-bin-download to defer binary downloads. Pull request #2195
- Engine adds configuration::ensure for atomic seed-if-empty initialization. Pull request #2214
- Compose now derives stable default configuration IDs from namespace and container key instead of using arbitrary values. Pull request #2212
- Startup displays download progress for package artifacts with per-worker status rows and progress bars. Pull request #2175
- Native musl iii-worker artifacts for
x86_64and aarch64 are now published and automatically selected on Alpine. Pull request #2192 - Compose startup can now be cancelled with Ctrl+C during lock waiting, metadata resolution, or artifact downloads. Pull request #2190
- Package metadata resolution now happens concurrently instead of sequentially, respecting the existing III_COMPOSE_MAX_PARALLEL_WORKERS limit. Pull request #2186
- JavaScript and Rust dependencies updated: OpenTelemetry to 2.x and 0.32, ws to 8.21. Pull request #2196
- Cargo and npm dependencies updated to close security advisories and gate supply chain checks in CI. Pull request #2197
Why it matters
This week brings installation improvements for unattended setups, better composition of workers with pre-configured environments, and critical reliability fixes for startup cancellation and configuration consistency. Download progress visibility and concurrent metadata resolution speed up the developer experience, while Alpine musl support and dependency updates extend platform compatibility and security.
Changelog entry
- Feat(install): add --non-interactive and III_NON_INTERACTIVE environment variable to skip setup prompts Pull request #2211
- Feat(install): add --start-with, --need-envs and --skip-bin-download flags to the setup offer Pull request #2195
- Fix(install): accept single keypress at harness tour prompt without requiring Enter Pull request #2189
- Feat(configuration): add atomic seed-if-empty ensure Pull request #2214
- Fix(compose): scope default configuration IDs by namespace with readable prefix and 16-character digest Pull request #2212
- Feat(compose): show startup download progress with per-worker status rows and progress bars Pull request #2175
- Fix(compose): make startup cancellable with Ctrl+C during lock waiting, metadata resolution, and downloads Pull request #2190
- Fix(compose): resolve package metadata concurrently using III_COMPOSE_MAX_PARALLEL_WORKERS limit Pull request #2186
- Fix(worker): publish native musl iii-worker artifacts for
x86_64and aarch64 on Alpine Pull request #2192 - Fix(compose): inherit machine environment in workers and apply
env_fileentries in declaration order Pull request #2203 - Fix(compose): preserve
env_filevalues for blank environment entries Pull request #2191 - Fix(compose): replace variant mapping when
config_overridechanges its name Pull request #2188 - Fix(compose): find workers after YAML comments including comments at column zero Pull request #2185
- Fix(cli): honor III_URL in iii trigger Pull request #2167
- Fix(cli): read the compose file's engine url in iii trigger Pull request #2168
- Fix(deps): move OpenTelemetry to JS 2.x / Rust 0.32 and ws to 8.21 Pull request #2196
- Chore(security): close remaining advisories and gate supply chain in CI Pull request #2197
- Fix(worker): publish lean runtime and builder Docker images Pull request #2182
- Fix(compose): a terminal operation event stops claiming a dead worker is ready Pull request #2176
- Feat(telemetry): report each completed onboarding tour step Pull request #2184
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.