Skip to content

Memory Vault

v1.0.7 Feature

This release adds 3 notable features for engineering teams evaluating rollout.

Published 7d MCP Developer Tools
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai-memory claude hybrid-search knowledge-graph mcp pgvector
+3 more
postgresql llm self-hosted

Summary

AI summary

The memory-vault CLI now works after pip installation.

Changes in this release

Dependency Medium

Docker base image downgraded to Python 3.13‑slim for full wheel coverage.

Docker base image downgraded to Python 3.13‑slim for full wheel coverage.

Source: llm_adapter@2026-07-19

Confidence: high

Bugfix Medium

`memory-vault` CLI now works after pip install.

`memory-vault` CLI now works after pip install.

Source: llm_adapter@2026-07-19

Confidence: high

Bugfix Medium

Version in `pyproject.toml` now matches git tag after install.

Version in `pyproject.toml` now matches git tag after install.

Source: llm_adapter@2026-07-19

Confidence: high

Full changelog

Memory Vault 1.0.7

Patch release focused on packaging correctness. If you install Memory Vault with pip install memory-vault, this is the release that makes the memory-vault CLI actually work.

memory-vault CLI is now pip-installable. Every subcommand (status, migrate, ingest, search, mcp, api, token, space, diagnose) failed with ModuleNotFoundError: No module named 'src' immediately on invocation for pip-installed deployments across every prior 1.0.x release. Docker deployments accidentally kept working because they bypassed the broken install with PYTHONPATH=/app + a raw source-tree copy. The refactor moves the code under a proper memory_vault package, updates the entry point, bundles the SQL migrations with the wheel, and removes the Docker workaround so containers and pip installs now share a single, correct install path. (#76, #84)

pyproject.toml version now tracks the git tag. The package reported version 0.4.0 regardless of which 1.0.x tag was installed, because the release workflow never bumped the version file. A one-time correction to 1.0.6 (now 1.0.7) plus a version-guard job in release.yml prevent the drift from recurring: future tags fail early if pyproject.toml doesn't match. (#75, #78)

Docker base image aligned to Python 3.13. Docker used python:3.14-slim, but spaCy (a heavy C-extension dependency) has no cp314 wheel yet — Python 3.14 is very recent and its wheel ecosystem hasn't caught up. Every docker build on main failed at pip install. Base image downgraded to python:3.13-slim, which has full wheel coverage across all deps and matches the CI pytest matrix. Also added a dependabot.yml ignore entry to prevent automatic bumps back to the bleeding edge. (#79, #80)

  • Windows ProactorEventLoop startup warnings on stdio MCP deployments with remote Postgres. Reproduces on Windows 11 + Python 3.12 + psycopg async pool. Needs a controlled repro before choosing the fix. Landing in a future patch. (#77)

  • Docker: docker pull ghcr.io/mihaibuilds/memory-vault:1.0.7 (or docker compose pull if using the standard compose file).

  • pip: pip install --upgrade memory-vault. First release where the console script actually works after pip install.

The packaging bugs in this release were surfaced by @git-pharos via an unusually thorough diagnostic bundle in #74. The bundle exposed not just the reported issues but the underlying pip-install breakage and the version-frozen state, which drove three of the four fixes above.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Memory Vault

Get notified when new releases ship.

Sign up free

About Memory Vault

All releases →

Related context

Earlier breaking changes

  • v1.0.4 Existing all-in-one image unchanged; drop‑in replacement for v1.0.3, but introduces new separate mcp-only image.

Beta — feedback welcome: [email protected]