Runtime 0.7.2: retain the upgrade recovery point after local writes
Runtime 0.7.2 carries the upgrade-plan write-watermark protection merged in Runtime PR #148. It preserves the existing retrieval behavior, point identity, stored payloads, embedding configuration, authorization rules and four scoped MCP tools.
A plan cannot resume across a local Runtime write
Each saved upgrade plan records the current write watermark from its profile's
local Ledger. apply and resume compare that value again while holding the
profile writer lease. If this Runtime committed a write after the plan was
created, status reports write_since_plan, and resume refuses to continue
with the old plan.
The refusal keeps the old plan and its backup reference available for review.
An operator can explicitly run upgrade plan --replace to archive that plan
and backup reference before creating a fresh plan. A plan saved by a Runtime
version without watermark support cannot resume, even when no local write
occurred, because it has no recorded watermark; explicitly replace that legacy
plan. For a plan that includes a watermark and has no local write across the
plan boundary, resuming an interrupted upgrade reuses its recorded embedded
backup only while that backup still exists and passes verification, instead of
creating a second recovery point. If the recorded backup is missing or unusable,
resume first attempts to recover a verified backup for the same plan instance.
If none can be recovered, it stops before further target changes and requires
upgrade plan --replace.
Scope boundary: the watermark observes writes recorded by this Runtime in the local profile Ledger. It cannot observe another Runtime process using a separate Ledger, another profile or device, or direct writes from other clients to Qdrant. It does not protect an entire Qdrant Cloud destination. Stop or isolate every other writer and take the provider's normal snapshot before an upgrade that requires a stable destination.
The watermark does not migrate data, change embedding models or dimensions, rebuild the collection, or change retrieval defaults. It is upgrade-plan protection only.
Compatibility
Runtime 0.7.2 keeps the existing storage and policy schemas. Existing memories remain in place. No migration, re-embedding or index rebuild is required. Hermes Catalog and the independent MCP distribution keep their own pins; this release preparation does not change either pin.
Installation
Check PyPI for availability before installing in a private environment:
python -m pip install 'hermes-plugin-qdrant-memory[mcp]==0.7.2'
For an existing destination, review upgrade status and upgrade plan before
applying. Keep the original plan identifier when resuming a watermark-enabled
interrupted upgrade that is not stale. Plans saved before watermark support
must be replaced even when no local write occurred. If a local write made a
supported plan stale, retain its recovery point and review the blockers before
explicitly replacing it.
Metadata
Release files for hermes-plugin-qdrant-memory 0.7.2
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.2.tar.gz | 487.3 kB | With provenance | Details for hermes_plugin_qdrant_memory-0.7.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hermes_plugin_qdrant_memory-0.7.2-py3-none-any.whl | Python 3 | none | any | Details for hermes_plugin_qdrant_memory-0.7.2-py3-none-any.whl |
Total release size: 671.3 kB
Release files / hermes_plugin_qdrant_memory-0.7.2.tar.gz
| Download URL | hermes_plugin_qdrant_memory-0.7.2.tar.gz |
|---|---|
| Size | 487.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a02a1e8971b348736b811410d2d366e230fe407051b8c0424c4766f6aa4ad775
|
|
BLAKE2b-256 checksum How to use checksums |
cce1eafe6372c3902b5d96a007f1e65d6de792bf777edf605b8131a23750bbf2
|
| 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 18, 2026.
Transparency logRelease files / hermes_plugin_qdrant_memory-0.7.2-py3-none-any.whl
| Download URL | hermes_plugin_qdrant_memory-0.7.2-py3-none-any.whl |
|---|---|
| Size | 184.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c0e5e82dc11eccff7f67ceaaa40caaa8df6396b14fbad7f55ceb116b6cf9efb9
|
|
BLAKE2b-256 checksum How to use checksums |
c6f186921d149f9ee29a66253b400643b9f205235fb8936eb2d521c1cf70d08a
|
| 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 18, 2026.
Transparency logSecurity for hermes-plugin-qdrant-memory 0.7.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.
Attestation for hermes_plugin_qdrant_memory-0.7.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 18, 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.