BlueTusk
GitHubGet Started
Getting started · docs/releases/1.1.0-rc.1.md

BlueTusk 1.1.0-rc.1 release record

Review the immutable 1.1.0-rc.1 tags, workflow runs, 65 public packages, verification record, product changes, and stable-release boundary.

4 min read722 wordsSource synchronized
View source on GitHub
ON THIS PAGE

BlueTusk 1.1.0-rc.1 release record

Published: 2026-08-29

Release commit: 2e735ed46aec11d5009158a00ca7b862f9ec12af

Channel: public release candidate (rc on npm; explicit prerelease on NuGet)

BlueTusk 1.1.0-rc.1 is the first coordinated public 1.1 package train across Provider, Streams, Sync, Live, Control Plane, Continuous Graph, and all three Live browser clients. It preserves the 1.0 public contracts while exposing the performance, allocation, batching, bounded-concurrency, and incremental graph work for production-like evaluation.

Published inventory

Registry Inventory Version behavior
NuGet 62 BlueTusk.* packages Exact version 1.1.0-rc.1
npm @bluetusk/live, @bluetusk/live-angular, @bluetusk/live-react rc points to 1.1.0-rc.1; latest remains 1.0.0

All six release tags resolve to the same commit:

  • provider-v1.1.0-rc.1
  • streams-v1.1.0-rc.1
  • sync-v1.1.0-rc.1
  • live-v1.1.0-rc.1
  • control-plane-v1.1.0-rc.1
  • continuous-graph-v1.1.0-rc.1

RC artifacts are immutable. A correction is published as rc.2; packages at rc.1 are never replaced.

Verification record

The protected release workflows completed successfully at the release commit:

Family Workflow run
Provider 33225555247
Streams 33227465140
Sync 33227966505
Live 33228526989
Control Plane 33229129438
Continuous Graph 33229550446

Post-publication verification confirmed:

  • all 62 NuGet packages and all three npm packages were available publicly;
  • every internal package dependency resolved to 1.1.0-rc.1;
  • npm rc resolved to 1.1.0-rc.1 while latest remained 1.0.0;
  • a clean isolated .NET 10 application restored the six family root packages and built with zero warnings and zero errors;
  • a clean npm application installed all three clients with zero reported vulnerabilities; and
  • the active repository ruleset retained 35 required checks and protected, non-bypassable publication environments.

NuGet publication used the package-prerelease trusted-publishing environment and a BlueTusk.* package policy. Stable publication remains isolated in the separate package-production environment.

What changed

Provider and EF Core

  • Reduced allocation and synchronization on command, pool, batch, reader, COPY, and EF update hot paths.
  • Retained the 16-workload Npgsql 10.0.3 comparison matrix and explicit saturated-pool coverage.
  • Preserved ADO.NET behavior, public API baselines, cancellation, session reset, and PostgreSQL-native type semantics.

Streams

  • Reused bounded transaction assembly state and reduced tuple/payload copies.
  • Preserved transaction ordering, stable identity, spooling, replay, and acknowledge-after-durability semantics.

Sync

  • Writes NATS envelopes into exact-sized buffers, streams OpenSearch NDJSON, reuses PostgreSQL binary payload memory, and retains ordered Redis batches.
  • Preserved retry, quarantine, reconciliation, rebuild, and connector-specific atomicity contracts.

Live

  • Added affected-key snapshot mutation and coalesced browser reducer updates.
  • Shares immutable serialized fan-out payloads while retaining bounded queues, replay, authorization, and slow-client policy.

Control Plane

  • Uses set-based inventory reads, bounded cross-instance concurrency, short-lived single-flight snapshots, and source-generated JSON metadata.
  • Preserved audit-before-mutation, fencing, authorization, and compatibility envelopes.

Continuous Graph

  • Added immutable compiler impact plans and a three-tier maintenance engine: trusted CDC deltas, authoritative key-scoped GRAPH_TABLE queries, and fail-closed full authoritative repair.
  • Added per-tier metrics, affected-key/query counts, fallback reasons, provenance indexes, and bounded ordered result maintenance.
  • Direct CDC projection remains explicit opt-in and requires complete old/new columns, replica identity, schema fingerprint, changed-column information, and the original security contract.

Read the performance leadership report and Continuous Graph guide for the detailed contracts. Performance evidence is workload-specific; this RC does not make an unsupported “faster everywhere” claim.

Install

Pin exact versions:

dotnet add package BlueTusk.Data --version 1.1.0-rc.1
npm install --save-exact @bluetusk/live@1.1.0-rc.1

See the installation guide for package selection, EF Core, Angular/React clients, and verification.

Stable 1.1.0 boundary

This publication does not authorize stable 1.1.0. The stable train remains blocked until all exact-stable-candidate gates are bound to one immutable commit, including:

  • digest-pinned PostgreSQL 19 GA and the post-GA SQL/PGQ matrix;
  • the required Streams, Sync, Live/Control Plane, and Continuous Graph endurance sequence;
  • complete final-SHA Windows/Linux performance evidence and confidence gates;
  • required security, compatibility, NativeAOT/trimming, package-consumer, documentation, supply-chain, provenance, and SBOM checks; and
  • independent review and operational acceptance records.

The official PostgreSQL project currently identifies 19 as Beta 3 and plans GA for September 2026; see its beta guidance and roadmap.

Applications may evaluate the RC against real workloads, but must define their own SLOs, capacity limits, recovery plan, and rollback criteria. Report defects with the exact package version, PostgreSQL version, deployment topology, reproduction, and redacted diagnostics.