You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 415a042
Browse filesBrowse the repository at this point in the historyBrowse files
chore(release): bump to 0.21.0 and document the upgrade
0.21.0 rather than a patch: it adds --split-identifiers, changes what
every camelCase symbol is embedded from, and re-embeds existing indexes on
first open.
Moves every release pin together: Cargo.toml and the workspace members in
Cargo.lock, both ENGINE_VERSION pins (fetch-engine.js, shared with the VS
Code client, and the JetBrains resolver), the npm package, both version
fields in server.json, the VSIX version, pluginVersion, and the VSIX
install examples in both READMEs.
Left at 0.20.1 on purpose: lsp4ijVersion, which is the LSP4IJ dependency
and only coincidentally matches; the comments and README lines that name
0.20.1 as the last release without vector stamps; and the test fixtures
that publish and download their own fake release.
The README gains an "Upgrading to 0.21" section. The upgrade guidance
existed but sat inside the flags table, where nobody upgrading would look.
It also says something nothing else did: graphs persisted by 0.20.1 can
already hold files its watcher let in from excluded directories, and stale
symbols from workspaces reached through a symlink. The fixes stop new
damage but do not remove what is already stored, so those users need one
reindex.
The clients now ask for v0.21.0 release assets, which do not exist yet.
package-npm.sh refuses to package until they are published.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017rVbt7rENTwXkdHt3Bpgb5
Copy file name to clipboardExpand all lines: README.md
+25-1Lines changed: 25 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ The server indexes the current working directory automatically.
30
30
Install the VSIX:
31
31
32
32
```bash
33
-
code --install-extension codegraph-0.20.1.vsix
33
+
code --install-extension codegraph-0.21.0.vsix
34
34
```
35
35
36
36
One VSIX serves every platform.
@@ -85,6 +85,30 @@ one tool and exits without the MCP stdio handshake — ideal for scripting.
85
85
86
86
---
87
87
88
+
## Upgrading to 0.21
89
+
90
+
Each project re-embeds once, in the background, the first time 0.21 opens it.
91
+
Stored vectors now record the model and settings that built them, and an index from 0.20.1 or earlier records none.
92
+
Keyword search keeps working while it runs.
93
+
94
+
Restart any `--watch` daemon after upgrading.
95
+
A daemon left running keeps writing vectors that 0.21 will not load, and sessions attached to it run without semantic search until it restarts.
96
+
97
+
Identifiers whose words run together, like `getUserById`, are now also embedded in word-split form.
98
+
This mostly helps natural-language search in camelCase languages such as TypeScript, Java and C#.
99
+
Pass `--split-identifiers=false` to keep the old behaviour.
100
+
101
+
`--full-body-embedding=false` now takes effect; in 0.20.1 the flag was always on.
102
+
103
+
Run a reindex once (`codegraph_reindex_workspace`) if either of these applied to you:
104
+
105
+
- you excluded generated directories with `--exclude` or `.codegraphignore`, because 0.20.1's file watcher still let changes to them into the graph;
106
+
- your workspace path goes through a symlink (on macOS that includes anything under `/tmp`), because 0.20.1 kept the old symbols of every edited or deleted file.
107
+
108
+
Both are fixed, but symbols already persisted by 0.20.1 stay until the graph is rebuilt.
0 commit comments