v0.0.11

Before you upgrade

Until the first public release, nothing upgrades a database in place. A build whose database schema differs from the one your instance holds refuses to start on it, changes nothing in the file, and says so in its log. The build that wrote the file can still read it, so going back to that build brings the instance back.

To carry your data into this build, take an export with the build that wrote the file (GET /export?format=archive), start this build on a fresh file, and restore the archive there (POST /restore). Until the first public release an archive is read only by the build that wrote it, so that restore can refuse the archive. Keep the export and the old build until the restore has answered.

In the container image, a refused database leaves the container running and unhealthy, with the message in its log, rather than restarting it into the same refusal. deploy/README.md says what to do next.

What's Changed

• refactor(server): compile type and filter SQL in one place by @aicayzer in #2066
• test(core): hold a stop fixture's page until the stop is set by @aicayzer in #2065
• refactor(server): read the time through one clock module by @aicayzer in #2067
• test(core): hold the stream clock still where a test counts waits by @aicayzer in #2078
• fix(server): hold the source filter at every door by @aicayzer in #2077
• fix(types): check array elements and say no file writes in-folder by @aicayzer in #2079
• feat(conformance): restart, move the clock and set faults through a stated target interface by @aicayzer in #2068
• docs(readme): draw the architecture diagram in one plain style by @aicayzer in #2081
• feat(server): expire feed items by a type's retention policy by @aicayzer in #2080

Full Changelog: v0.0.10...v0.0.11