Skip to content

regiondb v1.1.0

Latest
Latest

Choose a tag to compare

View all tags
@Filo6699 Filo6699 released this 31 Jul 03:46
v1.1.0
This tag was signed with the committer’s verified signature.
Filo6699 Filo6699
GPG key ID: 2104AF6959F09D81
Verified
Learn about vigilant mode.
f244231
This commit was signed with the committer’s verified signature.
Filo6699 Filo6699
GPG key ID: 2104AF6959F09D81
Verified
Learn about vigilant mode.

v1.1.0 is a stable, backward-compatible feature release on the v1.x line.

Highlights

  • Bounded world reads: deterministic paginated CHUNKSCAN plus CHUNKRANGE and CHUNKRADIUS with checked coordinates, a 256-chunk limit, and a 64 MiB encoded response cap.
  • Persisted chunk versions, single-chunk compare-and-swap, and atomic conditional multi-chunk commit decisions with crash-recoverable intents.
  • WALFLUSH as a global recoverability barrier in every steady-state durability mode, plus stable snapshot generations for concurrent read-only loads.
  • Optional ZRLE for checkpoint images and CHUNKBINC responses, fixed-cardinality Prometheus metrics, and the read-only regiondb-verify integrity scanner.
  • Recency-based bounded cache with second chances, a bounded maintenance queue, inline backpressure, and deterministic drain on shutdown.

Security

  • No default token ships in any artifact or image; an auth-enabled server refuses to start with an empty token, and token source precedence is logged without the value.
  • Intent paths are validated for grammar and containment, slot writes are bounds-checked before mutation, and temporary files are created exclusive/no-follow where supported.

Compatibility

Existing RGDBSPL1, RGDBSPL2, RGDBWAL1, and RGDBWAL2 data remains readable. RGDBSPL3 checkpoint images and version/generation/intent metadata are forward additions; opening newer data with an older binary is not promised. Wire protocol version 1 keeps its grammar, framing, error codes, and semantics for existing commands. fs_region_v1 remains experimental, opt-in, and outside all guarantees.

Upgrade and rollback

Stop the writer and back up the data directory before upgrading. v1.1.0 opens v1.0.0 directories without an offline conversion; once a chunk is rewritten or a WAL replayed, rollback to an older binary is not guaranteed — restore the backup instead. Geometry must remain unchanged when reopening a directory.

Artifacts

Linux, macOS, and Windows archives for amd64 and arm64, each with a Syft JSON SBOM, verified against SHA256SUMS.

Full notes: docs/releases/v1.1.0.md — see also the changelog.

Assets 15
Loading