Skip to content

chore(release): bump version to 0.3.0#171

Merged
pilotspacex-byte merged 1 commit into
mainfrom
release/v0.3.0
Jun 10, 2026
Merged

chore(release): bump version to 0.3.0#171
pilotspacex-byte merged 1 commit into
mainfrom
release/v0.3.0

Conversation

@pilotspacex-byte

@pilotspacex-byte pilotspacex-byte commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Release prep for v0.3.0

Bumps the crate version 0.2.0 → 0.3.0 and rolls [Unreleased] into [0.3.0] — 2026-06-11.

Release headlines (since v0.2.0, 50 commits)

Pre-release gates

  • Security review of full v0.2.0..main diff: no blocking issues (1 medium latent/unreachable code_len note in compaction.rs:554, tracked as follow-up)
  • Perf/correctness review of full diff: no blocking issues (buffer reuse, atomic ordering, SQ8 math, segment-install handoff all verified)
  • Local CI parity on Linux VM: fmt + clippy (default & tokio/jemalloc) green; test suites in flight
  • GitHub CI green on main head c88ad02 (CodeQL failure there is a SARIF-upload token flake, analysis itself passed)

After merge: tag v0.3.0 on the merge commit → release.yml builds/signs/publishes all artifacts.

Summary by CodeRabbit

  • New Features

    • Hot-shard elasticity enabling dynamic cluster scaling
    • Enhanced vector engine with background HNSW compaction, SQ8 quantization support, per-shard memory budgeting, and hotkey detection
    • Pipelined SET/GET operation performance improvements
  • Bug Fixes

    • Various behavioral refinements and bug fixes

Release prep for the v0.3.0 tag:

- Cargo.toml/Cargo.lock: 0.2.0 -> 0.3.0. moon_version in INFO server
  derives from CARGO_PKG_VERSION, so tagging without this bump would
  ship binaries self-reporting 0.2.0 (release.yml does not validate
  tag-vs-crate version).
- CHANGELOG: roll [Unreleased] into [0.3.0] - 2026-06-11 with a release
  summary. Headlines: background FT compaction + segment merge (PR #165),
  SQ8 quantization across the full FT lifecycle (PR #166), deep-review
  hot-path perf pass +33%/+25% pipelined SET/GET (PR #168), HOTKEYS
  command + per-shard SpaceSaving sketch (PR #169), elastic per-shard
  memory budgets (PR #170), OBJECT wire-reachability fix, Cypher lexer
  logos 0.16 migration, dependency bumps.

Pre-release gates run on this tree:
- Security review (diff v0.2.0..main): no blocking issues.
- Perf/correctness review (diff v0.2.0..main): no blocking issues.
- Local CI parity (fmt, clippy default + tokio/jemalloc, tests both
  runtimes) on Linux VM.

author: Tin Dang
@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@coderabbitai

coderabbitai Bot commented Jun 10, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 93986fb2-a4f0-4555-94e3-21d6bb650ffa

📥 Commits

Reviewing files that changed from the base of the PR and between c88ad02 and c72c586.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (2)
  • CHANGELOG.md
  • Cargo.toml

📝 Walkthrough

Walkthrough

This PR marks the 0.3.0 release by updating the package manifest version from 0.2.0 to 0.3.0 in Cargo.toml and adding a corresponding changelog entry documenting the release date and highlights including hot-shard elasticity, vector engine improvements, and performance optimizations.

Changes

0.3.0 Release

Layer / File(s) Summary
Release version and changelog
Cargo.toml, CHANGELOG.md
Package version is bumped to 0.3.0 and a new release entry is added to the changelog documenting hot-shard elasticity, vector engine maturity (HNSW compaction, SQ8 quantization, per-shard memory budgeting, hotkey detection), and pipelined SET/GET performance improvements.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • pilotspace/moon#155: Related version bump and release documentation work in Cargo.toml and CHANGELOG.md.

Poem

🐰 A hop, a bump, a changelog's verse,
From 0.2 to 0.3, for better or worse!
Hot shards dance, vectors now gleam,
Our little release, the coder's dream. 🚀

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description deviates significantly from the required template, providing release headlines and pre-release gates instead of the mandated sections (Summary, Checklist, Performance Impact, Notes). Restructure the description to match the template: add a brief Summary section, complete the Checklist with CI results, note Performance Impact findings, and move release details to Notes.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: bumping the version from 0.2.0 to 0.3.0, which is the core purpose of this release PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/v0.3.0

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@pilotspacex-byte
pilotspacex-byte merged commit 3e376a1 into main Jun 10, 2026
10 checks passed
@TinDang97
TinDang97 deleted the release/v0.3.0 branch June 10, 2026 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants