Skip to content

chore(release): cut v0.4.0 #202

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TinDang97 merged 1 commit into from
Jun 22, 2026
Merged

chore(release): cut v0.4.0 #202

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,29 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

## [0.4.0] — 2026-06-22

Bundles 5 closed milestones (first ADD-recorded cut; see `RELEASES.md` for
attribution): **Shared-Nothing Integrity & Cross-Shard Latency** (3 carried) ·
**Multi-Core Throughput Hardening** (12 carried) · **Throughput Polish**
(3 carried) · **FTS Hardening** (8 carried) · **Graph Correctness & Cypher
Filtering**. Headlines: working FTS query combinators (OR / TEXT+TAG / NUMERIC)
with true total-matched counts and the O(M²) high-DF cliff gone; correct Cypher
inline-property narrowing, incoming-edge traversal after compaction, and >32
graph labels; WAL group-commit, cross-shard read fast-path, and off-event-loop
FT.SEARCH throughput wins. Per-change detail below.

### Risk-accepted (shipped, disclosed) — cross-shard read fast-path removed (PR #175)

The shared-nothing migration (PR #175) deleted the direct-`RwLock` cross-shard
read fast-path; cross-shard reads now route through the owner shard's SPSC ring,
so cross-shard-read cells regress versus the pre-migration lock-read. This is a
**signed RISK-ACCEPTED waiver** (owner: Tin Dang) carried into this release, with
a follow-up task **cross-shard-read-acceleration** (lock-free cross-shard read
acceleration) tracked to land before **2026-08-01**. No correctness impact —
consistency is 197/197 across 1/4/12 shards on both runtimes; the cost is latency
on the cross-shard read path only.

### Docs — Verified cross-arch GCloud benchmark confirms v3-1 FTS + v3-2 graph fixes (PR #194)

Re-ran the 4-feature concurrent-vs-competitor benchmark (KV / Vector / Graph / FTS
Expand Down
2 changes: 1 addition & 1 deletion Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "moon"
version = "0.3.0"
version = "0.4.0"
edition = "2024"
rust-version = "1.94"
description = "A high-performance Redis-compatible server written in Rust"
Expand Down
7 changes: 7 additions & 0 deletions RELEASES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Releases

## v0.4.0 — 2026-06-22
milestones: v1-shared-nothing, v2-performance, v2-1-throughput-polish, v3-1-fts-hardening, v3-2-graph-correctness
waivers: shardslice-migration
evidence: Full CI matrix green on moon-dev (fmt + clippy default/tokio + test release/tokio, MOON_BIN-pinned ELF); detailed notes in CHANGELOG [Unreleased]; waiver shardslice cross-shard-read disclosed (follow-up cross-shard-read-acceleration, expires 2026-08-01)