Skip to main content

Runtime 0.6.2: receipt-scoped failed-event recovery

Runtime 0.6.2 adds receipt-scoped recovery for lifecycle events that were persisted but later marked FAILED. An authenticated retry validates the event's stored operation plan, requeues only its failed operations and returns the event to PENDING. It does not reset unrelated writes or re-extract the turn. QUARANTINED events remain operator-controlled, and malformed plans fail closed.

Runtime 0.6.1 behavior, the SQLite ledger format, Qdrant collection schema, vector dimensions, embedding fingerprints, scope boundaries and writer leases remain unchanged. No data migration or re-embedding is required. The Owner lifecycle route remains opt-in and still requires its existing authorization and scope checks.

Install this release

Confirm version 0.6.2 is available on PyPI before installing:

python -m pip install 'hermes-plugin-qdrant-memory[mcp]==0.6.2'
qdrant-memory --help

This installs the standalone CLI and MCP base without Hermes. Add the local extra for optional CPU embeddings or the remote extra for the authenticated Owner service. Model preparation requires explicit approval. Configure a private profile before memory operations. See the standalone guide, CPU setup and Owner guide.

Upgrade from 0.6.1

Install into the environment that already uses the intended private profile. Keep the same profile, Qdrant collection and embedding pipeline. After upgrading, run qdrant-memory status and qdrant-memory verify before resuming writes. The release does not automatically retry failed events; a client must make an authorized retry request for the same event receipt.

Publishing Runtime does not publish or update the generic MCP distribution, Codex plugin, DSH bundle, WorkBuddy launcher or Hermes Plugin Catalog. Each integration keeps its own version pin and release checks.

Metadata

Release files for hermes-plugin-qdrant-memory 0.6.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hermes-plugin-qdrant-memory 0.6.2
File Size Uploaded Provenance Actions
hermes_plugin_qdrant_memory-0.6.2.tar.gz 450.7 kB With provenance Details for hermes_plugin_qdrant_memory-0.6.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for hermes-plugin-qdrant-memory 0.6.2
File Interpreter ABI Platform Actions
hermes_plugin_qdrant_memory-0.6.2-py3-none-any.whl Python 3 none any Details for hermes_plugin_qdrant_memory-0.6.2-py3-none-any.whl

Total release size: 614.8 kB

Release files / hermes_plugin_qdrant_memory-0.6.2.tar.gz

Download URL hermes_plugin_qdrant_memory-0.6.2.tar.gz
Size 450.7 kB
Tags Source
SHA-256 checksum
How to use checksums
012956be71c7a59a096cca35a6cb339990f8a7d5ecc121166b29d425f2ae57b8
BLAKE2b-256 checksum
How to use checksums
2f4f7887b95542a652ea0288ae5de0b0b6909230aa9b351a4d98a6261131691e
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 12, 2026.

Transparency log

Release files / hermes_plugin_qdrant_memory-0.6.2-py3-none-any.whl

Download URL hermes_plugin_qdrant_memory-0.6.2-py3-none-any.whl
Size 164.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4606d1529092104d5594866032c61a02376c127f2ffc483c0442a7549b40c264
BLAKE2b-256 checksum
How to use checksums
a1a6874753af6915a8e00e547b69111d00f653eb9d8913d7cb0857ef06786c91
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 12, 2026.

Transparency log

Security for hermes-plugin-qdrant-memory 0.6.2

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.

Select from 2 files

Attestation for hermes_plugin_qdrant_memory-0.6.2.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 12, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page