Repository navigation
v0.37.0
Backups of any size, and rules that say what they mean
v0.37.0 finishes the items left from the review in v0.36.0: backups over 128 MB restore from an upload, back-relations in rules gain the ? operators and :each (and refuse comparisons that never worked), and a set of slow paths do far less work.
Fixed
- A backup over 128 MB couldn't be restored from an upload. The admin now sends a backup in 32 MB pieces and the server restores from them put together, so any size works; a piece that fails is sent again. The API:
POST /api/v1/admin/restore/uploads, aPUTper piece, thenPOST …/uploads/<id>/finish. - A queue worker or cron job that never ended held its slot for good. The slot now waits one more time limit for the run to end, then is released with a warning in the log.
- Back-relations (
_via_) in rules and filters:?=and the other?operators work on them (comments_via_post.status ?= "flagged"), and so does:each, comparing each record's value with its field's type.:lengthcounts the records, and is0for none on Postgres too (it was NULL there).- A filter through
@collectionor_via_no longer fails for non-admins when the joined collection's list rule is admin-only and its view rule holds a value.
- On Postgres, a fraction compared with a date, a bool,
created,updatedor a:lengthfailed the request (created > 1.5). It compares as SQLite does. - A malformed session cookie answered 500. It counts as signed out now.
Faster
- A record's history, read by anyone but an admin, checks the view rule once per version without re-parsing it, and pages in the database when there's no view rule (counting past 2,000 versions).
- CSV export pages by key instead of by offset; deleting a record that many others point to with
setNullreads them once; the orphaned-file sweep looks records up per batch; the MCP endpoint builds its tool registry once per schema change; vector search loads its matches in one query; a search compiles its filter once; startup reads the collection list once.
SDKs
No SDK changes: JS SDK 0.10.0 and Dart vaultbase 0.6.0 (with vaultbase_flutter 0.1.5) work with this release.
See the changelog for the full list.
Upgrade notes
- Rules with a plain comparison on
_via_(=,!=,<,>,= nullwithout:length) are refused when saved. One saved before denies every request (it never matched on SQLite and failed on Postgres); the server log names each at startup. Change it to?=(some record matches),:each(every one does) or:length.~and!~keep working. - Upgrade notes for earlier releases apply if you are coming from before v0.36.0.
Full Changelog: v0.36.0...v0.37.0