1.8.0 and 1.7.3 are released: Versions rows (1.8.0, 1.7.3), supported versions (1.8.x; 1.7.x has security fixes until 31 January 2027), FAQ, and every "coming in 1.8.0" note now "new in 1.8.0", with its links
Example outputs as 1.8.0 prints them: explain({ analyze }) of a reader's first query now counts the chunk directories it reads (157 bytes more here), so Core Concepts and two Recipes show slightly more bytes read
FAQ: the latest release is 1.7.2; Security Model: the CLI also reads JAZMIN_UNLOCK_TOKEN; Home: the Node.js note
Home: transactions, the group writer and the reader cache (coming in 1.8.0)
Versions: a 1.8.0 row marked coming, a 1.8.x column, limits per key and the edit-limits writer feature for older releases, new features and behaviour changes in 1.8.0, the new Node.js minimums
Errors and Troubleshooting (coming in 1.8.0): the Brotli refusals, verify() findings, transaction and group-writer refusals, changed()/refresh() on bytes, regroup, JazminFileChangedError, .NET OpenTable after Dispose
Performance and Tuning (coming in 1.8.0): opening after appends, the group writer, the reader cache, verify(), regroup, the JS writer's per-chunk memory, .NET trigram index memory, JS filter allocation, change files and grants with many keys; benchmark commands; checklist rows
Viewer and Browser, editable documents (coming in 1.8.0): a file changed on disk (Open again, JazminFileChangedError), opening after many appends in the browser, keys spanning thousands of partitions, filters allocating less; limits per key on what a key may send back
Security, Brotli and CVE-2026-111497 (coming in 1.8.0): the Node.js releases with the fix, the JS library refusing Brotli on others (JAZMIN_ALLOW_BROTLI=1 for backported builds), change files and submissions with Brotli refused by both libraries, the browser reader not affected; Node minimums on Home, Quick Start, CLI and Versions
write() with regroup: true (coming in 1.8.0): shared files whose partitions arrive mixed, its figures and rules; options table, Updating and CLI advise mention it
Server Side: readers kept open (changed(), refresh(), JazminReaderCache with leases; a reader whose lease opened a lock is not reused), its figures, and the group writer for many small writes (coming in 1.8.0); Reading: the new reader methods, .NET disposing twice
Updating: batch writes and transactions (beginAppend, openWriter) with the clash rules, upserts where the last row for a key wins (decimal, empty, NaN and Infinity keys), opening after many appends, Windows retries while a file is replaced (coming in 1.8.0)
verify() and jazmin check (coming in 1.8.0): every section checked, not only those a query reads; what each kind of file catches, the preamble and trailer values, publisherBytes, the quick check of a plain file and what it leaves out
Verified Publishers: SmithSoft's roots come in 1.8.1, not 1.8.0; a 1.8.0 library or viewer shows signed files as signed by an unknown key, never certified
Versions: 1.7.2 (grantAccess security fix)
Command-Line-Tool: jazmin verify (coming in 1.8.0)
Verified Publishers: framed as a further layer of trust and security; certified results rest on SmithSoft's published roots
Verified Publishers (coming in 1.8.0): verifying, results, what the viewer shows, good to know
1.7.1: Versions row; estimate() in the browser reader
Viewer and Browser: the browser reader's files() is a method
1.7.0: document pages (Embedded Files and Documents), the masked-columns demo, Versions rows
1.7.0: progress and Stop, estimate(), reverse reading, text orders, bounded-memory rewrites, the browser script in parts, list: false and actions by file group, locked files and key services, Masked Columns page, online documents; Versions page (release row, compatibility, features, supported 1.7.x)
Versions: 1.6.2
Versions: 1.6.1
Time-limited access: the sample key service without the owner key, and the from-disk two-factor demo
1.6.0 released: next-release labels become (1.6.0), anchors follow, Versions page (release row, compatibility, supported 1.6.x); examples now run against 1.6.0
Several Tables: how tables are named while renamed; set values checked first
Figures measured again (three runs each, own processes): a new sort order 5.4-6.1 s in JavaScript, 6.6-6.9 s in .NET; a re-key of 20 rows 2.1-2.2 s
Several Tables: adding, removing and renaming tables, links between tables, changing several tables at once (next release); update table, versions and benchmarks rows
Changing indexes and the sort order (next release): update({ indexes, sortedBy }), its benchmark and the versions table