Skip to content

Memory Vault

v1.0.6 Bugfix

This release fixes issues for SREs watching stability and regressions.

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

✓ No known CVEs patched in this version

Summary

AI summary

Fixed OCI annotation casing for io.modelcontextprotocol.server.name to match GitHub org login.

Changes in this release

Bugfix Medium

Corrects casing of `io.modelcontextprotocol.server.name` OCI annotation on `memory-vault-mcp`.

Corrects casing of `io.modelcontextprotocol.server.name` OCI annotation on `memory-vault-mcp`.

Source: granite4.1:8b-q6_K@2026-05-19

Confidence: high

Full changelog

Patch release — corrects casing of the io.modelcontextprotocol.server.name OCI annotation on memory-vault-mcp. No behavior changes; drop-in replacement for v1.0.5.

What's fixed

The MCP Registry compares the OCI ownership label against the GitHub login casing exactly. The label value was lowercase (io.github.mihaibuilds/memory-vault) but our GitHub org login is mixed case (MihaiBuilds). Publishing to the registry was blocked with a 403 until this is corrected.

Fix: label value is now io.github.MihaiBuilds/memory-vault to match the org login.

Upgrade

docker compose pull
docker compose up -d

Or pin explicitly:

docker pull ghcr.io/mihaibuilds/memory-vault:1.0.6
docker pull ghcr.io/mihaibuilds/memory-vault-mcp:1.0.6

170 tests passing in CI on Python 3.14 + Postgres 16 + pgvector. Both images built multi-arch (amd64 + arm64).

Full changelog

Compare: v1.0.5...v1.0.6

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]