Changelog
Every product-visible change to RowShield is recorded on this page, newest entry first.
The format is deliberately plain so it can be skimmed, searched or parsed: each entry carries an ISO date, a tag naming the affected surface — rules, probe, cli or web — and a short description of what changed for someone using the product. Internal refactors, dependency bumps and administrative work do not appear, because they change nothing you can observe.
How to read the changelog
Entries are append-only and never rewritten, so links into this page remain stable. Breaking changes are marked in the entry itself and state what action, if any, is needed from you; most entries require nothing. Dates mark when the change reached production, not when it was written.
Where a change alters a verdict's meaning — tightening what counts as a leak finding, for example — the entry says so explicitly, because silent changes to judgement are worse than the change itself.
Current entry: launch window, 31 August 2026
[rules] Nine rules ship at launch, covering row security switches, missing and tautological policies, role coverage, public storage buckets, exposures observable from outside, and grant widening. Each rule carries its own documentation page describing the detection and the fix.
[probe] The anonymous-key probe goes live: full-table reads over the public REST surface with row counts recorded, storage bucket listing, and per-table verdicts distinguishing denied-by-default from genuinely empty.
[cli] The command line interface reaches version one: local scans running the same nine rules, exit codes wired for pipeline use, and full driver-level diagnostics printed locally when a connection fails.
Following along
The page renders as ordinary HTML with stable anchors per entry, so following it is a matter of whatever polling or fetching arrangement suits you. Substantive changes are additionally summarised in release notes inside the application, and anything affecting availability appears on the status surface rather than here.
Suggestions about what deserves an entry belong in feedback. The bar is simple: if a change is visible to you, it gets a dated line on this page.
Did this answer your question? If not, tell us what is missing — article corrections go straight to the person who maintains it.