Changelog

Highlights

• Versioning/docs: bumped workspace crate manifests and docs/install/readme references to 0.27.6.
• Release contract: this is a non-breaking patch release; runtime and API behavior are unchanged from 0.27.5.

Highlights

• Benchmark surface correction: the public Rust PostgreSQL benchmark now measures qail-rs from native Qail ASTs against pgx SQL strings instead of starting qail-rs from raw SQL.
• Aggregate fast path: grouped scalar aggregate results now use the dedicated four-column zero-copy receive path with tighter query/pipeline buffer reuse.
• Current benchmark read: the March 30 one-round native snapshot was a 15 / 15 throughput sweep; the latest March 31 median refresh is the live canonical read and stays positive on 13 / 15 throughput slices, all five p50 slices, and three of five p99 slices.
• Versioning/docs: workspace crates and docs references were bumped to 0.27.4.

Highlights

• Semantic parity: chained or_filter(...) behavior is now consistently preserved as grouped predicate intent (AND (... OR ...)) across runtime SQL generation paths.
• Regression coverage: parser/transpiler/encoder parity checks were extended to prevent future OR-to-AND behavior drift.
• Versioning/docs: workspace crates and docs references were bumped to 0.27.3.

Highlights

• Idempotency isolation: request fingerprints now include behavior-changing headers (prefer, x-transaction-id, x-branch-id, x-qail-result-format).
• Anonymous replay safety: unauthenticated requests now bypass idempotency caching to prevent cross-client key collisions when auth is disabled.
• Branch overlay correctness: update overlays now patch matching rows by PK, preserve PK identity for branch-only rows, and get-by-id can resolve branch-only overlays.
• Branch lifecycle hardening: overlay read/write/merge/stats SQL paths now operate only on active branches, branch create fails when parent is missing/inactive, and branch delete returns not found for non-active/non-existent branches.
• Auth gate ordering: branch read endpoints now enforce branch-admin authorization before DB execution.
• Versioning: workspace crates bumped to 0.27.2.

Highlights

• QWB2 strictness: binary endpoint now rejects legacy QWB1/raw-text payloads and uses strict QWB2 AST decode for ingress.
• Safety: binary AST decode now applies explicit payload limits to prevent unbounded allocation on malformed payloads.
• Gateway benchmark parity: release notes include text-vs-binary gateway benchmark validation under identical endpoint shape.
• Versioning: workspace crates bumped to 0.27.1.

Highlights

• Breaking API rename: standardized pipeline method names to pipeline_execute_* across driver/connection/pool surfaces (for example pipeline_batch -> pipeline_execute_count).
• Pipeline strategy: added AstPipelineMode (Auto, OneShot, Cached) plus plan surfaces AutoCountPlan and AutoCountPath.
• Prepared AST handle: added PreparedAstQuery with dedicated prepared AST execution APIs for repeat-query hot paths.
• Encoder fast path: added AstEncoder::encode_cmd_sql_reuse(...) for caller-buffer SQL/param reuse.
• Runtime hardening: cached AST pipeline now rolls back newly registered statements on encode/protocol failures and improves desync resilience.
• Policy behavior: gateway policy engine now denies when policies exist but none match table/operation, while preserving allow behavior for an empty policy set.
• Versioning: workspace crates bumped to 0.27.0.

Highlights

• Strict ordering: destructive/rename hints (drop*, rename) now execute before declarative create paths in strict migration compilation.
• Policy verification: migrate apply now validates policy state by final expected (table, policy) after all commands in a migration complete.
• Reliability: drop-and-recreate policy sequences in a single migration no longer fail from intermediate-state checks.
• Tests: added strict policy replace ordering coverage and final-intent expectation tests.
• Versioning: workspace crates bumped to 0.26.6.

Highlights

• Coverage: added forced QAIL_PG_IO_BACKEND=io_uring startup-path smoke tests.
• Tooling: added scripts/check-io-uring-linux-cross.sh for Linux cross-target validation with local zig fallback support.
• Runtime introspection: added PgConnection::transport_backend() for telemetry and verification.
• Feature wiring: removed stale tokio-uring coupling, added native-io-uring alias, and retained io_uring compatibility.
• Versioning: workspace crates bumped to 0.26.5.

Highlights

• Versioning: workspace crates bumped to 0.26.3.
• Docs/readmes: refreshed installation snippets and version references to 0.26.3.

Highlights

• Startup: default StartupMessage protocol is now 3.2 (196610).
• Compatibility: explicit protocol-version rejection triggers a one-shot retry using protocol 3.0 (196608).
• Wire decode: backend NegotiateProtocolVersion ('v') is now parsed and handled.
• Cancel path: cancel secret keys are now bytes-native (4..=256) with legacy i32 wrappers retained for compatibility.
• Hardening: integration tests now cover startup negotiation and downgrade boundaries.
• Versioning: workspace crates bumped to 0.26.2.

Highlights

• CI: fixed publish workflow breakage after tenant-only runtime cutover.
• Gateway: binary examples aligned to QWB1 wire format.
• Packaging: crate metadata/readme parity updates across release-track crates.
• Versioning: workspace crates bumped to 0.26.1.

Highlights

• Breaking: removed RlsContext::operator(...) and runtime operator-scoped aliases in favor of tenant-only constructors.
• Breaking: gateway runtime auth resolves tenant scope from tenant_id only; legacy operator_id claim no longer maps tenant context.
• Gateway: fixed policy evaluation to avoid premature deny when later matching allow policies exist.
• Gateway: expanded optimize_qail_for_execution(&mut cmd) coverage for consistent execution planning.
• Analyzer: reduced false positives from comment/string-literal noise and tightened semantic diagnostics.
• SDK/Docs: direct SDK support surfaced for TypeScript, Swift, and Kotlin; Node.js native binding remains deferred.
• Versioning: workspace crates bumped to 0.26.0.

Highlights

• CLI: added migrate down --force with non-TTY unsafe guard and wait-for-lock support.
• CLI: added JSON output mode for migrate analyze.
• Migrations: optional HMAC signing support for migration receipts.
• Migrations: advisory locks now scoped by database with stronger timeout diagnostics.
• Integrity: receipt signature verification enforced on apply and rollback paths.
• Versioning: workspace crates bumped to 0.25.1.

Breaking Changes

• qail-core: removed raw SQL helpers including Qail::raw_sql(...).
• qail-pg: removed direct raw-SQL APIs from the primary runtime contract in this release line (later versions may expose compatibility wrappers for legacy tests/examples).
• Encoder: AST runtime path no longer allows raw SQL pass-through.

Migration Guidance

• Use AST-native builders (Qail::get/add/set/del, typed filters, typed joins).
• Use session AST commands (Qail::session_set, session_reset) instead of raw strings.
• Legacy raw examples moved behind legacy-raw-examples and disabled by default.

Highlights

• PG auth: decode support for auth code 6 (AuthenticationSCMCredential) with explicit startup guidance.
• PG URL aliases: added krbsrvname, gsshostname, and gsslib compatibility mappings.
• Tests: added regressions for SCM auth decode and GSS URL alias parsing.

Notable Changes

• v0.24.5: docs domain moved to dev.qail.io, snippets/version references aligned.
• v0.24.4: standardized wording around SQL strings vs protocol bytes across docs.
• v0.24.2: added skip_locked support and user-scoped RlsContext::user(user_id).