Repository navigation
sessionFlow v1.3.1
Voyager v1.3.1
Bug-fix release, 2026-11-11. No schema change - the core bridge schema stays
1, so this is fully compatible with the DSH plugin v1.2.0 (which requires
schema 1); no plugin change is needed.
What's fixed
- Windows stdin was decoded as the ANSI code page. A Chinese query sent to
voyager apiwas silently read through GBK, so{"query": "\u4f1a\u8bdd\u8bb0\u5f55"}searched
for garbled bytes and answeredcount: 0even though the sessions existed.
The UTF-8 force now lives where stdin is actually read (api.serve()), so
voyager api,python -m voyager.apiandpython -m voyager.api serveare
all covered. The regression test assertscount, never the echo - a GBK echo
of the UTF-8 bytes renders as plausible CJK, which is exactly why this defect
survived for so long. voyager api serve- the documented command - exited 2 without ever
serving. Both argument parsers accepted only the implicit default and died on
unrecognized arguments: servebefore reading a single request, so the shipped
VS Code sidebar could never have worked. Both parsers now acceptserveas a
no-op verb; an unknown verb is still a usage error.
Carried into this release from the 1.3.1 line:
- DSH
session.v4.jsonl.zstddiscovery (sessions written after the rename were
invisible) plus a warning for session-shaped files no known pattern claims. - Windows stdout forced to UTF-8 at the entry point so non-ASCII titles no
longer arrive as U+FFFD over the bridge. - Short phrases (< 3 characters, e.g.
voyager search \u8865\u4e01) now take a literal
instr()scan instead of returning 0 rows. - Grok on Windows no longer leaves an extra console open after quit.
Tests
- Removed two hard-coded
E:/code/voyagerpaths intest_scan_streaming.py
(issue #20). They now
deriveREPO_ROOTfrom__file__and pass it to children viaPYTHONPATH,
matchingtests/test_scan_crash.py. No product code changed.
Upgrade
No migration. Your index is read as-is; nothing is rewritten, so rolling back to
1.3.0 is safe.
Install or upgrade, pinned to this tag:
pipx install "voyager[all] @ git+https://github.com/HarryHeYu/sessionFlow.git@v1.3.1"Voyager is not published to PyPI - the
voyagername is already taken, so
installation is from the tagged source above.voyager upgradedoes not exist;
re-run the command above (bump the tag) to move to a newer release. The
@v1.3.1pin is what makes a reinstall reproducible, and what the DSH plugin's
own error messages recommend.
Compatibility
- Core bridge schema: 1 (unchanged).
- DSH plugin: v1.2.0 (requires schema 1) - compatible.
- Python >= 3.10; Windows / macOS / Linux.
- Full suite: 1379 passed, 6 skipped (6 skips are platform/environment-specific).