Runtime 0.7.1: keep the recovery point and stop on unresolved receipts
Runtime 0.7.1 fixes two upgrade-safety defects reported against the published 0.7.0 wheel. It does not change dense retrieval, point identity, stored payloads, the embedding fingerprint, authorization, confirmed writes or the four scoped MCP tools.
Interrupted upgrades keep their recovery point
In 0.7.0, a normal upgrade plan after an interrupted apply replaced the saved
state with a fresh planned record. The backup directory still existed, but
status lost its path and the step history. The same plan_id could return as
if nothing had run.
Runtime 0.7.1 reads the saved record inside the existing writer lease. A plan
that has executed a step and has not reached ready keeps its phase, failure,
step records and recovery-point reference. upgrade plan reports the existing
plan identifier and tells the operator to resume it.
If the plan is stale, upgrade plan --replace archives the old plan and its
backup reference before it saves a new plan. An operator never has to delete a
control-plane file by hand.
apply and resume re-read the plan after they take the lease. If another pass
replaced the plan while the lock was acquired, the older plan is refused and the
newer record is not overwritten. A repeated resume reports already_applied
without a second backup or policy generation.
When an embedded backup exists without its step record, resume reopens the
copy and checks the planned point count. It then adopts the existing path. An
interrupted activation is reported complete only after the committed policy
record matches the target and the live destination still satisfies the verify
step.
Shared Owner receipts block planning and apply
In 0.7.0, an admitted Shared Owner lifecycle receipt was visible to the normal
write interlock but not to the upgrade planner. The receipt had no terminal event. plan could omit the blocker and apply could report ready.
Runtime 0.7.1 reuses the read-only condition from
qdrant_memory/shared_state.py for both call sites. It covers
owner_events_v1 receipts without a terminal event and incomplete
shared_requests_v1 rows. A receipt whose event is already terminal remains a
crash leftover and does not block.
plan reports the blocker. apply and resume recheck after taking the lease,
so a receipt that appears after planning is still caught. Existing reset,
scoped-delete, failed-event and quarantined-event blockers are unchanged.
Maintenance commands never clear receipts, re-extract a turn or replay a pending
event. Complete the existing Owner recovery flow first, then resume the plan
when it is still valid, or use upgrade plan --replace when it is stale.
Compatibility
Runtime 0.7.1 keeps the 0.7.0 storage and policy schema. No data migration,
re-embedding, index rebuild or policy default change is included. Qdrant Server
1.20.1 remains the recommended self-hosted baseline, and the published
qdrant-client range is unchanged.
The separate qdrant-memory-mcp 0.3.4 distribution pins Runtime 0.7.0 and does
not receive this fix automatically. A later MCP patch can select 0.7.1. This
Runtime release does not change the Hermes Catalog pin, and it does not request
an upstream Catalog update.
Installation
Check PyPI for availability before installing in a private environment:
python -m pip install 'hermes-plugin-qdrant-memory[mcp]==0.7.1'
For an existing destination, keep the same profile, collection and embedding
pipeline. Run upgrade plan, review the blockers and index status, then apply
inside a short maintenance window. A failed or interrupted pass is resumed with
its original plan identifier, not replanned by default.
See the 0.7.0 release for the initial policy upgrade design.
Metadata
Release files for hermes-plugin-qdrant-memory 0.7.1
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.7.1.tar.gz | 483.5 kB | With provenance | Details for hermes_plugin_qdrant_memory-0.7.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hermes_plugin_qdrant_memory-0.7.1-py3-none-any.whl | Python 3 | none | any | Details for hermes_plugin_qdrant_memory-0.7.1-py3-none-any.whl |
Total release size: 666.1 kB
Release files / hermes_plugin_qdrant_memory-0.7.1.tar.gz
| Download URL | hermes_plugin_qdrant_memory-0.7.1.tar.gz |
|---|---|
| Size | 483.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a27114e7a070037961b44ad17c34c436a1260b2acab976c634a5ec146b00935
|
|
BLAKE2b-256 checksum How to use checksums |
03b968eaae0f54f31a02b37c561977d7776bcff63abfc5cc3213116225adfa41
|
| 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 15, 2026.
Transparency logRelease files / hermes_plugin_qdrant_memory-0.7.1-py3-none-any.whl
| Download URL | hermes_plugin_qdrant_memory-0.7.1-py3-none-any.whl |
|---|---|
| Size | 182.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0cbb7ed46dbe1eac191e51e076601c2744dc21dd108db03bf17e357b60aea75a
|
|
BLAKE2b-256 checksum How to use checksums |
6264838ddc25e0a6100c6df25faba8053566aead49d45979bdfcb0dd25fc115c
|
| 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 15, 2026.
Transparency logSecurity for hermes-plugin-qdrant-memory 0.7.1
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.7.1.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 15, 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.