Repository navigation
HyperbyteDB 0.9.3-beta - #128
Conversation
Version bump to 0.9.3-beta, with release notes (docs/user-guide/release-notes-0.9.3-beta.md). The Python client, still at 0.9.1b0, is 0.9.3b0.
PR SummaryLow Risk Overview Adds This diff is version metadata and user-facing release documentation; the behavioral changes are described in the release notes and referenced issues (#119–#127), not in the files touched here. Reviewed by Cursor Bugbot for commit 8ed286d. Configure here. |
The CA bundle step's text changed, so its cache key did: a cached build re-runs it.


Version bump to 0.9.3-beta, with release notes (
docs/user-guide/release-notes-0.9.3-beta.md). The Python client, still at0.9.1b0, becomes0.9.3b0; the JS and Rust clients were already 0.9.3-beta.A correctness and security release. 0.9.2-beta and earlier:
Also in this release:
top/bottom/sample, and working subqueries over aggregates (Add TOP, BOTTOM and SAMPLE; fix subqueries over aggregates #127)cluster.peersformation (Promote cluster.peers learners as they catch up; no 503 after /health is 200 #126)X-Hyperbytedb-Version(Add X-Hyperbytedb-Version #120)The runtime image stages now fail if the CA bundle still has the eMudhra root. Their apt step changed, so the release build re-runs it even with the layer cache.
Pair with operator v0.3.3 once it's out (hyperbytedb-operator #19, #20): it fixes backups (
minio/mccan no longer be pulled) and restarts each pod once per update. v0.3.2 runs 0.9.3-beta.