BlueTusk 1.1.0 coordinated release line

BlueTusk 1.1.0 is one coordinated, API-compatible performance release across all six product families and the three Live browser clients. The existing 1.0 artifacts are immutable; 1.1 adds optimised paths and observability without removing 1.0 contracts.

Public release candidate 1.1.0-rc.1 was published on 2026-08-29 from exact commit 2e735ed46aec11d5009158a00ca7b862f9ec12af. See the RC release record for tags, workflows, package inventory, registry checks, installation, and stable-release boundaries.

Family changes

• Provider carries forward the validated ac702d7 performance and allocation work and expands the reference programme to concurrency, Linux, TLS, and constrained-network variants.
• Streams removes redundant envelope copying, reuses bounded transaction assembly state, and retains pooled segmented spooling and ordered ack.
• Sync emits exact-sized NATS envelopes, streams OpenSearch NDJSON, uses zero-copy PostgreSQL binary payloads, and retains ordered atomic Redis batches.
• Live adds affected-key snapshot mutation and batched Angular/React updates while retaining bounded subscriber queues and one immutable fan-out payload.
• Control Plane adds set-based inventory, bounded instance concurrency, single-flight caching, and source-generated API serialization.
• Continuous Graph adds the three-tier maintenance engine, compiler impact plans, explicit CDC trust contracts, scoped authoritative queries, ordered delta maintenance, fail-closed repair, and per-tier metrics.

Compatibility and publication

All family version properties and npm manifests target 1.1.0. Stable publication remains disabled; the public RC is enabled only through the isolated prerelease train. The stable candidate must pass the cross-product performance contract, exact endurance sequence, PostgreSQL 15–19 and package gates, independent review, and the external coverage-guided handoff. Continuous Graph and stable publication additionally require a digest-pinned PostgreSQL 19 GA image. Tags are created in dependency order only after those gates resolve to one final commit.

See the performance leadership report and Continuous Graph guide.