Repository navigation
v3.18.2 — Server Downgrade Guard
Patch release for the VS Code extension; the engine is unchanged. The crate, /openapi.json, pip and MCP serverInfo move to 3.18.2 only so every surface keeps reporting one version. Everything in the v3.18.0 notes (Loop-Ready Contract) and the v3.18.1 notes (Version Alignment) still applies.
What's fixed
| Fix | Before | Now |
|---|---|---|
| A newer running server is kept | The extension reused a healthy server only when isServerVersionAcceptable passed (same major.minor, or an exact match under hipcortex.strictServerVersion); otherwise it stopped the server and started its own bundled binary. A window still on an older extension therefore downgraded a newer server onto data that server had written — on 2026-09-29 a 3.17.0 window replaced a 3.18.1 server about 70 s after it started. |
shouldReuseRunningServer reuses a healthy server newer than the bundled EXPECTED_SERVER_VERSION in both modes (numeric x.y.z compare in isServerNewerThanExpected) and logs that the extension should be updated. An unhealthy server, or an older one outside the policy, is still replaced. |
| Version shown | @hipcortex /help and the activation log said v3.14.0 in every release since 3.14.0 |
Both read the installed extension's package.json; a test fails if a literal Extension vX.Y.Z string returns to extension.ts |
| Marketplace links | The README's ../LICENSE, ../docs/*.md and package.json links returned 404: vsce resolved them against the repository root, not vscode-extension/ |
release.yml and npm run package:vsix pass --baseContentUrl and --baseImagesUrl for vscode-extension/; a test checks every vsce package call |
Reload every VS Code window after updating. The guard lives in the extension: a window still running an extension older than 3.18.2 replaces a newer server exactly as before.
Upgrade note (unchanged from 3.18.0): once 3.18 has written IntentExpire entries, downgrading to ≤ 3.17 is unsupported — older binaries skip unknown kinds when restoring the tx counter and can reuse tail tx ids. The fix above stops the extension from causing that downgrade.
Test coverage
VSIX jest 106/106 — six new tests, and the health-check test no longer expects the 3 s timeout that 3.13.0 raised to 30 s (3.18.1: 99/100); CI's VS Code extension tests job passes again. 379 lib + 597 unit + 194 integration + 59 property + 270 Python = 0 failures in the petgraph build; web-server route_parity_sit 7/7.
Channel state
| Channel | Version |
|---|---|
| GitHub (this release) | 3.18.2 — platform binaries + hipcortex-memory-3.18.2.vsix attached by release.yml |
PyPI (pip install hipcortex) |
3.18.2 |
| VS Marketplace / Open VSX | uploaded by hand from this release's VSIX |
npm (hipcortex) |
registry serves 0.5.2; TypeScript SDK source is 3.12.0 and lacks the 3.13+ methods |
| crates.io | not published |