See what is tested—and what is still pending.
Every release claim links to evidence. Passed checks, open work, package history, security, and performance results are shown separately and without hidden assumptions.
Explore the current results.
Public 1.1 RC packages
All 62 NuGet packages and three npm clients are public at 1.1.0-rc.1 and resolved in clean consumers.
All six product releases passed
Provider, Streams, Sync, Live, Control Plane, and Continuous Graph were built from the same source commit.
Clean application install
A new .NET 10 application built with all six product families, and all three npm clients installed with no reported vulnerabilities.
PostgreSQL matrix
Provider, replication, compatibility, and feature tests run against five PostgreSQL generations.
PostgreSQL 19 full matrix
3,289 passed with zero failures across 45 test assemblies; 158 environment-specific cases were not executed.
ADO.NET live compatibility
Functions, procedures, IN/OUT/INOUT rows, Dapper, schema APIs, DI and health checks passed.
Official EF Core tests
1,987 passed; 124 are skipped by the official upstream EF Core suite.
Parser-finding review
Nine parser test targets are ready. The latest run passed six and stopped safely on three; those results need independent review and a rerun on the exact release candidate.
Intentional test credentials
All 22 test credentials are recorded and restricted to localhost or disposable test systems. Any unknown value or external host stops the check.
External scanner disposition
The pull request warnings match known test values, but an independent reviewer must still confirm that they are false positives.
Public APIs checked
13,056 API signatures are tracked across six products. An unreviewed change fails the build.
Memory-use checks
Automated memory limits cover commands, COPY, replication, EF, Live, Sync, and graph.
Package identity and contents
31 Provider packages and 29 symbol packages matched the expected source commit, file hashes, and software inventories.
All product packages verified
Every 1.1.0-rc.1 package is public and passed exact-version NuGet/npm installation tests.
Known dependency vulnerabilities
No known NuGet security advisory matched a direct or indirect dependency in the checked build.
Initial Brotli budget
The Angular production build enforces raw and compressed startup, lazy-chunk and complete-distribution budgets with hashed assets and no source maps.
Field Core Web Vitals
The public host still needs 100 field samples over 28 days with p75 LCP ≤2,500 ms, INP ≤200 ms and CLS ≤0.1.
Streams 72-hour test
The test and automatic result checker are ready, but the required successful 72-hour run is not complete.
Sync 24-hour test
Stable Sync waits until the exact candidate completes and passes its 24-hour test.
Planned failure-and-recovery tests
The long-running Streams and Sync tests must each recover from seven planned failures and save the results for review.
Live V1 implementation
Replay, permissions, transports, clients, security, load, stored formats, and package tests are implemented.
PostgreSQL 19 graph queries
Beta 3 is tested from a fixed container image. Stable support waits for the final PostgreSQL 19 release.
Production operations approval
Ten measured checks need external evidence and ordered approval; written assurances without measurements do not pass.
Final independent review
The exact release candidate still needs application trials, backup and restore checks, a rollback rehearsal, and maintainer approval.
See what is available and what comes next.
Public RC packages are available now. Stable release still requires the remaining tests and approvals shown here.
What this page does not claim.
1.1.0-rc.1is public on NuGet and npm; this page does not represent it as stable1.1.0.- Passing the code checks does not mean every production environment has been tested.
- Recovery can resend the final unconfirmed transaction. PostgreSQL and Redis commit state with the checkpoint, OpenSearch uses replay-safe versions, and NATS consumers keep the stable transaction ID beyond the broker's deduplication window.
- Stable Streams still needs its exact 72-hour run, and Sync still needs its exact 24-hour run, including the planned failure-and-recovery checks.
- SQL/PGQ turns on only when the server supports it, and stable PostgreSQL 19 support waits for the final GA release and its test results.
- Stable release still requires an independent review, real application trials, and tested backup, restore, and rollback procedures.