# openclaw-mem v1.9.24 release notes

- **Date:** 2026-05-28 (Asia/Taipei)
- **Type:** Patch / release hygiene
- **Release range:** `v1.9.21` → `v1.9.24`
- **Baseline:** latest previous GitHub Release was `v1.9.21`

## Summary

`v1.9.24` is a release-hygiene patch. It aligns the public version-reporting surfaces and publishes a catch-up GitHub Release covering the intervening `v1.9.22` and `v1.9.23` tags, which existed on the repository but were not published as GitHub Releases.

This release:

- aligns `openclaw_mem.__version__`, package metadata, and `openclaw-mem status --json` so they all report `1.9.24`,
- summarizes the public-facing changes that landed under the intervening `v1.9.22` and `v1.9.23` tags,
- retains the existing `v1.9.23` tag without rewriting it.

There is no new runtime behavior in `v1.9.24` beyond version-string alignment.

## Catch-up: what landed under intervening tags

### `v1.9.22` tag — optional Qdrant Edge retrieval backend wiring

Under the `v1.9.22` tag, `openclaw-mem-engine` gained optional, disabled-by-default wiring for a Qdrant Edge retrieval backend, including backend planning, runtime routing, a bounded bridge adapter, and a LanceDB fallback path. Public documentation was added for the Qdrant Edge implementation, lifecycle, no-restart enable flow, and live-activation runbook.

Safety posture under the `v1.9.22` tag, unchanged by `v1.9.24`:

- LanceDB remains the default backend and the canonical write owner.
- Qdrant Edge is an opt-in read-index / cache path only.
- No live runtime config change, no restart, and no write path is enabled by virtue of this release.

### `v1.9.23` tag — repository graph neighborhood experiment

Under the `v1.9.23` tag, a public, experimental, file-only workflow was added for repository graph neighborhood exploration:

- `scripts/repo_graph_neighborhood_experiment.py`
- `docs/repo-graph-ingest.md`

The experiment uses an upstream `knowledge-graph.json` as candidate Pack/Observe context. It does not write Store-side truth and does not install any live skill.

## What `v1.9.24` itself changes

- `openclaw_mem.__version__` reports `1.9.24`.
- Package metadata reports `1.9.24`.
- `openclaw-mem status --json` reports `version.openclaw_mem = "1.9.24"`.

The published artifact is otherwise behaviorally equivalent to the `v1.9.23` tag.

## Compatibility

- No runtime behavior change relative to the `v1.9.23` tag beyond version-string alignment.
- No configuration migration is required.
- No backend topology change: LanceDB remains default and canonical writer.
- No Gateway, plugin, cron, runtime config, Store, retrieval, or Pack/Observe behavior change.
- The `v1.9.23` tag is preserved on the repository and is not rewritten.

## Verification

Representative checks for this release:

```bash
python -c "import openclaw_mem; print(openclaw_mem.__version__)"
# 1.9.24

openclaw-mem status --json | python -c 'import json, sys; print(json.load(sys.stdin)["version"]["openclaw_mem"])'
# 1.9.24

python -m pytest -q tests/test_repo_graph_neighborhood_experiment.py
```

Expected results:

- `openclaw_mem.__version__` prints `1.9.24`.
- `openclaw-mem status --json` reports `version.openclaw_mem = "1.9.24"`.
- The repository graph neighborhood experiment tests pass.

## Versions

- `openclaw-mem`: `1.9.24`

Full changelog: see `CHANGELOG.md`.
