Changelog¶
All notable changes to the dbwarden Test Harness, newest first. The harness has
no tagged releases yet, so changes are grouped by the date they landed on
main.
2026-09-19¶
Changed¶
- dbwarden is resolved from the sibling
../dbwardencheckout. The lockfile points at the source through[tool.uv.sources]and the dependency floor is raised to0.19.0, so the harness exercises the latest source instead of the published wheel.uv sync --no-sourcesstill resolves PyPI for the distribution certification workflow. - The compatibility findings are closed. Every finding recorded against the
published
0.17.1wheel is fixed, along with the PostgreSQL identity, index sorting,NULLS NOT DISTINCT, and storage-parameter findings. See Known Findings by Release.
Added¶
- A
v0.19.0SQLite SQL contract baseline.0.19.0emitsAUTOINCREMENTfor a SQLite integer primary key, so the byte-level contract is approved per release. See SQL Contract Tests. dbwarden-redisin the required plugin matrix.
Removed¶
- A stale strict
xfailon MariaDB foreign-key ordering. The0.16.5fix is in, so the cell now passes.
Fixed¶
- CI checks out
dbwarden-org/dbwardenalongside the harness. Every job except distribution needs the sibling checkout for the path source; distribution certifies the published wheel withuv sync --locked --no-sources. - Ruff findings in the generative suites and tools are cleared under the current ruff version.