Repository navigation
Release 0.20.5 - #258
Merged
Merged
Release 0.20.5#258
Conversation
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Release 0.20.5 for the Devicor rollout. This bumps the version in
__init__.py,project.tomland the version pin tests, and moves CHANGELOG [Unreleased] to 0.20.5, following the pattern of #252.[0.20.5] - 2026-11-04
Added
memnet admin upgrade-verify --before <manifest>compares the running serve with the saved upgrade manifest: the same session ids, and the same rows and relations per session. Any mismatch exits 3. It runs client side, so it also checks a 0.20.4 serve.scripts/upgrade-rollback.shrestores the old venv link and the saved pre-upgrade state directory, then waits for the old serve to restore every session (docs/operations/safe-upgrade.md).typed_walkand CLImemnet query typed-walk --json-handles(one@WALKJSONline). Every node and edge is an opaque session-keyed handle; no nickname, hid or element id appears in the reply or its error text.starttakes a handle from an earlier row or a nickname. A handle from another session, or of a deleted node, is refusedstale_handle. Same limits as the CLI walk. MN-REQ-14.7 slice.Fixed
@WARN: restore_fallback.memnetruns in its own process (version,guide,examples,admin upgrade-verify, or underMEMNET_TEST_INLINE) now returns its own exit code; atyper.Exitcode was turned into 0.[mcp]extra — memnet-mcp without the [mcp] extra exits 2 with one line:pip install 'memnet-llm[mcp]'.Changed
where_type_mismatch. This replaces the 0.20.4 note that'000123'matches nothing.unknown_relation(CLI and MCP; checked after folding) instead of an empty walk.