-
Notifications
You must be signed in to change notification settings - Fork 86
release: stage Jina embedding migration for 0.2.5851 #738
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,41 @@ | ||
| # CodeDB 0.2.5851 | ||
|
|
||
| CodeDB 0.2.5851 begins a backward-compatible managed embedding migration. | ||
| Existing clients remain on Qwen while this release opts into the smaller, | ||
| faster Jina code model. Both routes remain available on the hosted service. | ||
|
|
||
| ## Compatibility behavior | ||
|
|
||
| - CodeDB 0.2.5850 and older continue to send the explicit model name | ||
| `Qwen/Qwen3-Embedding-0.6B`. | ||
| - CodeDB 0.2.5851 sends | ||
| `jinaai/jina-embeddings-v2-base-code` at 512 dimensions. | ||
| - Jina queries use its symmetric raw-text representation. Explicit Qwen and | ||
| custom-model overrides preserve the historical Qwen instruction prefix. | ||
| - ANN sidecars persist the model and vector-space identity. A Qwen sidecar is | ||
| never searched with a Jina query vector. | ||
|
|
||
| When a new client encounters an older Qwen sidecar, hybrid context remains | ||
| available through transient exact reranking. Run the explicit command below | ||
| once per previously indexed repository to build the Jina sidecar: | ||
|
|
||
| ```bash | ||
| codedb /path/to/repo semantic-index | ||
| ``` | ||
|
|
||
| The rebuild is intentionally not automatic: updating CodeDB must not silently | ||
| upload bounded source chunks from a repository. Rebuilding is transactional and | ||
| replaces only the prior semantic generation. | ||
|
|
||
| ## Operational notes | ||
|
|
||
| The hosted service runs Qwen and Jina concurrently and routes by the explicit | ||
| `model` field already sent by every released client. No API token, endpoint, or | ||
| configuration change is required. `CODEDB_EMBEDDINGS_MODEL` remains available | ||
| for explicit custom-provider and rollback configurations. | ||
|
|
||
| The Jina model is Apache-2.0 licensed. The pre-release evaluation found roughly | ||
| 2.0-2.3x higher indexing throughput and lower GPU memory use, while retrieval | ||
| quality remained workload-dependent. Keeping both routes live makes the | ||
| migration observable and reversible rather than forcing old installations onto | ||
| a different vector space. |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| pub const semver = "0.2.5850"; | ||
| pub const semver = "0.2.5851"; |
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When this release sets the native version to 0.2.5851,
npm/package.jsonremains at 0.2.5850. I checked.github/workflows/npm-publish.yml: it publishes the version read directly from that manifest, so the 0.2.5851 publish will instead attempt to republish the already-existingcodedeebee@0.2.5850and fail; additionally,npm/scripts/postinstall.jsderives the GitHub release tag from that same version. Update the npm manifest alongside the native release metadata.Useful? React with 👍 / 👎.