BlueTusk 1.0.0 publication record
Status: published on 2026-08-23.
BlueTusk 1.0.0 was published as six independently versioned product families
from release commit
7380d7b028c72b2aae348b778711d104d022a3f8.
Every release tag resolves to that commit. The temporary, repository-owner
release exception was removed by
6abb6365f1352fbb6d24a76d67f42d567800782b
after publication; the normal fail-closed release workflow and active main
ruleset are restored.
Publication evidence
| Family | Stable tag | NuGet packages | npm packages | Release workflow |
|---|---|---|---|---|
| Provider | provider-v1.0.0 |
31 | 0 | run 32643869503 |
| Streams | streams-v1.0.0 |
10 | 0 | run 32644411522 |
| Sync | sync-v1.0.0 |
8 | 0 | run 32644873113 |
| Live | live-v1.0.0 |
9 | 3 | run 32645259901 |
| Control Plane | control-plane-v1.0.0 |
2 | 0 | run 32645643697 |
| Continuous Graph | continuous-graph-v1.0.0 |
2 | 0 | run 32645983565 |
| Total | 6 tags | 62 | 3 | 6 successful runs |
Each run completed restore, formatting and documentation verification, the full build and test suite, direct and transitive dependency auditing, selected family packaging, package-content and provenance validation, CycloneDX/SPDX SBOM generation, artifact upload, GitHub build-provenance attestation, and protected production publication. NuGet authentication used GitHub OIDC; the npm packages were published as public packages with npm provenance.
Post-publication checks on 2026-08-23 confirmed HTTP 200 for every one of the
62 immutable NuGet 1.0.0 flat-container artifacts. The public npm registry
reported version and latest dist-tag 1.0.0 for:
Repository-owner release decision
The repository owner explicitly authorised immediate stable publication and accepted the following exceptions to the planned V1 evidence policy:
- independent approval was incomplete;
- coverage-guided fuzz evidence was not produced for the release commit;
- the reference performance gate had not passed;
- the exact endurance evidence was incomplete; and
- PostgreSQL 19 GA evidence was deferred.
These exceptions are release facts, not successful gate results. They do not change the standard release policy for later versions, and they do not turn the missing evidence into a production-readiness claim. No coverage-guided fuzzing workflow was triggered as part of this release operation.
NuGet inventory
The registry package IDs below are grouped by the family that owns their version and release tag.
Provider (31)
BlueTusk.ClientBlueTusk.DataBlueTusk.Data.DependencyInjectionBlueTusk.DiagnosticsBlueTusk.EntityFrameworkCoreBlueTusk.EntityFrameworkCore.DesignBlueTusk.Extensions.AbstractionsBlueTusk.Extensions.CitextBlueTusk.Extensions.Citext.EntityFrameworkCoreBlueTusk.Extensions.HStoreBlueTusk.Extensions.LTreeBlueTusk.Extensions.PgTrgmBlueTusk.Extensions.PgVectorBlueTusk.Extensions.PgVector.EntityFrameworkCoreBlueTusk.Extensions.PostGISBlueTusk.Extensions.PostGIS.EntityFrameworkCoreBlueTusk.Extensions.TestingBlueTusk.Extensions.TimescaleDBBlueTusk.Extensions.TimescaleDB.EntityFrameworkCoreBlueTusk.Identity.AwsBlueTusk.Identity.AzureBlueTusk.Identity.GoogleCloudBlueTusk.ProtocolBlueTusk.ReplicationBlueTusk.Replication.PgOutputBlueTusk.SecurityBlueTusk.SourceGenerationBlueTusk.TemplatesBlueTusk.ToolBlueTusk.TransportBlueTusk.TypeSystem
Streams (10)
BlueTusk.StreamsBlueTusk.Streams.AspireBlueTusk.Streams.CloudEventsBlueTusk.Streams.DependencyInjectionBlueTusk.Streams.EntityFrameworkCoreBlueTusk.Streams.Storage.FileBlueTusk.Streams.Storage.PostgreSqlBlueTusk.Streams.Storage.RedisBlueTusk.Streams.TestingBlueTusk.Streams.Tool
Sync (8)
BlueTusk.SyncBlueTusk.Sync.AspireBlueTusk.Sync.DependencyInjectionBlueTusk.Sync.NatsBlueTusk.Sync.OpenSearchBlueTusk.Sync.PostgreSqlBlueTusk.Sync.RedisBlueTusk.Sync.Testing
Live (9)
BlueTusk.LiveBlueTusk.Live.AspireBlueTusk.Live.AspNetCoreBlueTusk.Live.DependencyInjectionBlueTusk.Live.EntityFrameworkCoreBlueTusk.Live.GrpcBlueTusk.Live.ServerSentEventsBlueTusk.Live.SignalRBlueTusk.Live.Testing
Control Plane (2)
BlueTusk.ControlPlaneBlueTusk.Dashboard
Continuous Graph (2)
BlueTusk.ContinuousGraphBlueTusk.ContinuousGraph.ControlPlane
Post-release obligations
The published artifacts are immutable. A defect is corrected with a new
version; 1.0.0 is never overwritten. The deferred PostgreSQL 19 GA matrix,
endurance runs, reference performance evidence, independent review, and pilot
evidence remain open hardening work and must retain their real status in all
future readiness claims.