chore(release): v0.3.0

[raymondj99]

Summary

• Bump workspace version 0.2.1 -> 0.3.0
• Promote CHANGELOG [Unreleased] to [0.3.0] - 2026-05-17
• Updates internal crate version pins and Cargo.lock to match

Release contents

• Fielded observation indexing (title/summary/importance/source_kind/concepts/source_files)
• Memory-store schema v2 with forward-only migration
• memory_tier end-to-end (filter + stamp + read-back)
• New openmemory-eval crate and openmemory eval CLI subcommand
• Hybrid search now actually runs on every documented path
• MCP openmemory_search no longer double-pumps top_k * 3
• MCP URI-prefix filters no longer hide lower-ranked matches

Test plan

• cargo check --workspace --all-features passes locally
• CI green on this PR
• Merge then push v0.3.0 tag to trigger release workflow

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores

  • Released version 0.3.0 across the workspace.

• Documentation

  • Updated changelog with the 0.3.0 release information.

[coderabbitai]

Warning

.coderabbit.yaml has a parsing error

The CodeRabbit configuration file in this repository has a parsing error and default settings were used instead. Please fix the error(s) in the configuration file. You can initialize chat with CodeRabbit to get help with the configuration file.

💥 Parsing errors (1)

Validation error: String must contain at most 250 character(s) at "tone_instructions"

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

📝 Walkthrough

Walkthrough

This pull request releases version 0.3.0 by updating the workspace version in Cargo.toml from 0.2.1 to 0.3.0, synchronizing all internal member crate dependencies to match, and adding a dated changelog section header for the 0.3.0 release.

Changes

Release 0.3.0

Layer / File(s)	Summary
Version and changelog updates CHANGELOG.md, Cargo.toml	Workspace version is bumped to 0.3.0 in the package declaration, all internal workspace dependency versions are updated to 0.3.0, and a ## [0.3.0] - 2026-05-17 release header is added to the changelog to group the released changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A hop and a bump to 0.3,
Version strings dance in harmony—
Cargo and changelog align,
Release notes gleam, so fine! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(release): v0.3.0' directly and clearly matches the changeset, which updates the workspace version from 0.2.1 to 0.3.0 and promotes the CHANGELOG to reflect this release.
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 chore/release-v0.3.0

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CHANGELOG.md`:
- Around line 12-13: The changelog footer still points [Unreleased] to
v0.2.1...HEAD and is missing a [0.3.0] link; update the link references in the
footer so that [Unreleased] points to v0.3.0...HEAD (or remove Unreleased if you
want it closed) and add a new [0.3.0] entry mapping to v0.2.1...v0.3.0. Locate
the footer link block that contains the markers [Unreleased] and [0.3.0], adjust
the URLs/ranges accordingly, and ensure there is a new reference line for
[0.3.0] matching the repo release tag format used elsewhere.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1a565a9d-ac18-4f48-aeb2-d810f3c90cb7

📥 Commits

Reviewing files that changed from the base of the PR and between 9cd6bf5 and 8ad78fc.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• CHANGELOG.md
• Cargo.toml

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Update changelog reference links for the new release.

After adding 0.3.0, the footer references should also be updated so release links resolve correctly (Line 296 onward currently still points [Unreleased] to v0.2.1...HEAD and has no [0.3.0] entry).

Suggested patch

-[Unreleased]: https://github.com/raymondj99/openmemory/compare/v0.2.1...HEAD
+[Unreleased]: https://github.com/raymondj99/openmemory/compare/v0.3.0...HEAD
+[0.3.0]: https://github.com/raymondj99/openmemory/compare/v0.2.1...v0.3.0
 [0.2.1]: https://github.com/raymondj99/openmemory/compare/v0.2.0...v0.2.1

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	## [0.3.0] - 2026-05-17
	[Unreleased]: https://github.com/raymondj99/openmemory/compare/v0.3.0...HEAD
	[0.3.0]: https://github.com/raymondj99/openmemory/compare/v0.2.1...v0.3.0
	[0.2.1]: https://github.com/raymondj99/openmemory/compare/v0.2.0...v0.2.1

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` around lines 12 - 13, The changelog footer still points
[Unreleased] to v0.2.1...HEAD and is missing a [0.3.0] link; update the link
references in the footer so that [Unreleased] points to v0.3.0...HEAD (or remove
Unreleased if you want it closed) and add a new [0.3.0] entry mapping to
v0.2.1...v0.3.0. Locate the footer link block that contains the markers
[Unreleased] and [0.3.0], adjust the URLs/ranges accordingly, and ensure there
is a new reference line for [0.3.0] matching the repo release tag format used
elsewhere.

[codspeed-hq]

Merging this PR will not alter performance

✅ 19 untouched benchmarks

---

_{Comparing chore/release-v0.3.0 (8ad78fc) with main (8983580)¹}

Footnotes

1. No successful run was found on main (9cd6bf5) during the generation of this report, so 8983580 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩