Skip to content

v0.3.0

Choose a tag to compare

View all tags
@entelecheia entelecheia released this 01 Nov 07:20
· 86 commits to main since this release
v0.3.0
d1330a2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
  • A vault whose PII policy has members this build does not know (from a newer-format config) fails closed: note writes, check, tidy, promote-from-amem, promote, move and delete and log appends on it are refused with PII_POLICY instead of screening with an incomplete policy. Reads and vaults pii show still work.
  • Versions coexist on one machine (#82). vmem mcp loads every module a tool can run at startup, the agent-mem root included, so a running server keeps its own code and tool list when its install is replaced or a newer release is installed beside it.
  • vmem setup <target> --root <path> registers another install root, such as <install>/releases/<version>/, resolved to its real path. Without --root setup registers the running install as before.
  • vmem.config.json accepts an optional version (format 1). A config from a newer format is read tolerantly and its unknown keys survive registry writes; at or below format 1 unknown keys stay errors. Log screening accepts the same extended PII policy, and vaults pii --set refuses to replace a policy whose unknown members it would drop.
  • The derived index is indexes/<sha256>-links<N>.sqlite, named per link-resolution version, so two versions alternating on one vault no longer rebuild each other's links. The first run after upgrading builds it once.
  • vmem manifest --json lists the version, the config format, the MCP tool names and the CLI commands.
  • The embedded @staix/agent-mem pin moves from 0.11.0 to 0.17.0, at or above agent-mem's 0.13 floor for agent workflows.
  • N-1: 0.2.4 runs beside this release. It keeps its own unversioned index file and reads the config this release writes, since this release never adds version; 0.2.4 refuses a config that carries version or any other key it does not know.

Install

npm i -g @staix/vault-mem@0.3.0

Published to npm with provenance through GitHub OIDC trusted publishing. The validated tarball (SHA-256 8977b407f1734c97aca44bc830dacffb2f3ebd3820ee53965a0b9927675b94e9) and its manifest (tag, commit, SHA-256) from this run are attached.

Full changelog: v0.2.4...v0.3.0

Assets 4
Loading