Skip to content

v0.3.1

Choose a tag to compare

@h-wata h-wata released this 29 May 04:06
· 62 commits to main since this release
921bc2f

v0.3.1 Release Notes

A consistency + polish release on top of v0.3.0. No breaking changes — existing
installs keep working without any manual step.

Highlights

  • On-disk paths renamed mesh-memkioku-mesh (#128). kioku-mesh init
    now writes ~/.config/kioku-mesh/, the state dir defaults to
    ~/.local/share/kioku-mesh/, and init --install-systemd generates
    kioku-mesh-zenohd.service. This finishes the brand consistency the v0.3.0
    rename intentionally deferred. No automatic data migration: when only a
    legacy mesh-mem directory exists, kioku-mesh reads it as before and prints a
    one-time warning nudging a manual mv. The env-var prefix (MESH_MEM_*) and
    Python import name (mesh_mem) are intentionally unchanged.
  • kioku-mesh init guides the path to multi-host mesh (#96, PR #127):
    mode-specific follow-up hints after init (localhost → both scale-up paths;
    hub → a ready-to-run --mode spoke command pre-filled with the detected LAN
    IP; spoke → a hub-side --listen reminder), plus a full per-mode --mode
    description block and a "Picking a --mode" table in the README.
  • "Tier 1" demoted from a first-class architecture tier to a demo path
    (ADR-0013). The README architecture is now Local (SQLite, default) vs
    Mesh (zenohd + RocksDB, persistent); mesh start / mesh join are
    documented as a "try mesh without zenohd" demo with the ephemeral-replication
    caveat called out. Docs/CLI-help only — no runtime behavior change.
  • README restructured (#125, #126): hero + table of contents + Roadmap, a
    single end-to-end Quickstart, Operations folded under Power users.

Upgrade

No breaking changes.

uv tool install --upgrade git+https://github.com/h-wata/kioku-mesh.git
# or, after this release is on PyPI:
pip install --upgrade kioku-mesh

Optional: move data to the new path

Existing installs keep working from ~/.config/mesh-mem / ~/.local/share/mesh-mem
(with a one-time warning). To adopt the new paths, follow
docs/migration.md — stop zenohd + MCP servers, mv the
config/state dirs, update your zenohd systemd unit, and restart. The migration
guide includes how to identify an environment-specific zenohd unit before
stopping it.