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 for availability before installing in a private environment:
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 for the preceding Runtime behavior changes.
Metadata
Release files for hermes-plugin-qdrant-memory 0.6.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hermes_plugin_qdrant_memory-0.6.3.tar.gz | 451.7 kB | With provenance | Details for hermes_plugin_qdrant_memory-0.6.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hermes_plugin_qdrant_memory-0.6.3-py3-none-any.whl | Python 3 | none | any | Details for hermes_plugin_qdrant_memory-0.6.3-py3-none-any.whl |
Total release size: 615.9 kB
Release files / hermes_plugin_qdrant_memory-0.6.3.tar.gz
| Download URL | hermes_plugin_qdrant_memory-0.6.3.tar.gz |
|---|---|
| Size | 451.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5028892420bc7e45e9b9fdd638652b24bf6282638a482ebcb9516e20ec9eef3f
|
|
BLAKE2b-256 checksum How to use checksums |
0260f3232897e221b9fab3685e6a128da3de9323d042541fc8c8c77f32b9a7da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logRelease files / hermes_plugin_qdrant_memory-0.6.3-py3-none-any.whl
| Download URL | hermes_plugin_qdrant_memory-0.6.3-py3-none-any.whl |
|---|---|
| Size | 164.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6e9fb998fd685f7c25bc06f01e3564acb8f4ba4741eeb54f0d21ca0857251b6a
|
|
BLAKE2b-256 checksum How to use checksums |
301c451f6fdb1b9e7732d757277837bf3043dee2c949ed33b9f6a2d78ac58853
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logSecurity for hermes-plugin-qdrant-memory 0.6.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for hermes_plugin_qdrant_memory-0.6.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.