Metadata-Version: 2.4
Name: hermes-plugin-qdrant-memory
Version: 0.6.3
Summary: Durable Qdrant memory for Hermes, standalone CLI and local MCP
License-Expression: MIT
Project-URL: Homepage, https://github.com/cnkang/hermes-plugin-qdrant-memory
Project-URL: Repository, https://github.com/cnkang/hermes-plugin-qdrant-memory
Project-URL: Issues, https://github.com/cnkang/hermes-plugin-qdrant-memory/issues
Project-URL: Changelog, https://github.com/cnkang/hermes-plugin-qdrant-memory/blob/main/CHANGELOG.md
Project-URL: MCP, https://github.com/cnkang/qdrant-memory-mcp
Project-URL: Skill, https://github.com/cnkang/skills/tree/main/qdrant-memory
Requires-Python: >=3.11
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: qdrant-client<2,>=1.15
Requires-Dist: httpx<1,>=0.28
Requires-Dist: portalocker<4,>=3.2
Requires-Dist: jsonschema<5,>=4.23
Requires-Dist: pywin32<313,>=311; sys_platform == "win32"
Provides-Extra: mcp
Requires-Dist: mcp<3,>=1.30; extra == "mcp"
Provides-Extra: remote
Requires-Dist: mcp<3,>=1.30; extra == "remote"
Requires-Dist: uvicorn<1,>=0.35; extra == "remote"
Provides-Extra: local
Requires-Dist: fastembed==0.9.1; extra == "local"
Dynamic: license-file

# Runtime 0.6.3: explicit Hermes compatibility metadata

Runtime 0.6.3 declares `requires_hermes: ">=0.21.5"` in both native plugin
manifests. This is the existing compatibility floor, now available to Hermes
directory and packaged-plugin loaders as required by the current Catalog
admission rules. The floor is not raised. Runtime behavior, dependencies,
tool schemas, storage formats and embedding fingerprints are unchanged from
0.6.2.

The Hermes source-install examples and demo now resolve release tags to full
commit SHAs before passing `--ref`, as required by the current Hermes CLI.

The optional Shared Owner remains off by default. It retains 0.6.2 recovery:
retrying an authorized event receipt validates its saved operation plan and
requeues only that event's failed operations, without extracting the turn
again or reordering unrelated writes. Quarantined events remain under operator
control; failed events are not retried automatically.

## Installation

Check [PyPI](https://pypi.org/project/hermes-plugin-qdrant-memory/0.6.3/) for
availability before installing in a private environment:

```sh
python -m pip install 'hermes-plugin-qdrant-memory[mcp]==0.6.3'
```

For Hermes Catalog installations, wait for the separately reviewed Catalog
repin, run `hermes plugins update qdrant-memory`, and restart Hermes. A Runtime
publication does not update the Catalog automatically.

## Upgrade notes

From 0.6.2, keep the same profile, collection and embedding pipeline; no data
migration is needed. After upgrading, run `qdrant-memory status` and
`qdrant-memory verify` before resuming writes.

Catalog users upgrading from 0.5.4 must retain the same embedding pipeline to
reuse their collection. The optional CPU FastEmbed extra changed from 0.9.0
to 0.9.1, which changes its embedding fingerprint even with the same model and
dimensions. Preserve the old environment and data; to switch, export from the
old environment and re-embed into a new profile and collection. Do not reuse
the old CPU collection directly. Catalog PM installs only manifest dependencies,
not the optional CPU extra. Ollama users retaining their existing model and
embedding configuration are not affected by this FastEmbed change.

See the [0.6.2 release](0.6.2.md) for the preceding Runtime behavior changes.
