v2.4.5

HexDB 2.4.5 is a small follow-up to 2.4.4: tessellation names that clash with API routes are refused, and a hex that can't undo deletes says so.

Fixed

• Route names can't be new tessellation names. A tessellation named updates, a2a or ready could be created, but the API route of the same name hid it over REST. Those names are now refused for new tessellations, like queues, shares, mcp and quarantine since 2.0. A tessellation an earlier version created under one of them stays usable through SQL, GraphQL and transactions. A test now checks every route against the reserved names, so a new route can't be missed.

Added

• A warning when deletes can't be undone. With storage.trash_days = 0 (or files.trash_days = 0), deleted documents (or files) aren't kept, so their deletes can't be restored. The hex now says so in its startup log, in /status (storage.trash_warning) and on the admin UI's Deletes page.

Upgrading

Restart the hexes one at a time, as usual: replicas first, the Overseer last. Coming from 2.4.3 or earlier, read the 2.4.4 notes first: its storage format can't be read by earlier versions.

Full Changelog: v2.4.4...v2.4.5