chore(release): bump ruvector-core workspace to 2.3.0, ruvector-extensions to 0.1.2 - #685
Merged
Merged
Conversation
…sions to 0.1.2 Version bumps to publish the recently-merged Lattice embeddings work: - Workspace (ruvector-core + 25 sibling crates): 2.2.3 -> 2.3.0 (minor -- new opt-in `lattice-embeddings` feature is additive, no default-build changes). crates.io already has 2.2.3 published; this unblocks a new ruvector-core release. - ruvector-extensions (npm): 0.1.0 -> 0.1.2. Local package.json was stale -- the registry already had 0.1.0 and 0.1.1 published out-of-band, so 0.1.2 is the next available version. Note: neither package currently has a working automated publish pipeline (release.yml, the documented Rust release pipeline, fails with a workflow-file startup_failure; ruvector-extensions has never had CI publish coverage at all) -- publishing this round by hand with the equivalent gates run locally (full test suite incl. the lattice-embeddings feature, npm test suite via tsx since `npm test`'s plain glob silently only runs one of five test files, dry-run for both registries) in lieu of CI. Co-Authored-By: claude-flow <ruv@ruv.net>
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
1 participant
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.
Summary
Version bumps to publish the recently-merged Lattice embeddings work (#648, #651, #663, #664) and the CVE fixes (#672):
ruvector-core+ 25 sibling crates that inheritversion.workspace = true):2.2.3 -> 2.3.0. Minor bump — the newlattice-embeddingsfeature is additive/opt-in, no default-build behavior changes. crates.io already has2.2.3published, so this was required to publish anything new.ruvector-extensions(npm):0.1.0 -> 0.1.2. Localpackage.jsonwas stale — the registry already has0.1.0and0.1.1published out-of-band (no matching CI run for either), so0.1.2is the next available version.A process gap found along the way
Neither package currently has a working automated publish pipeline:
release.yml(the documented Rust crate release pipeline, per.github/workflows/RELEASE-FLOW.md) has failed with astartup_failure("workflow file issue") on every run for at least the past month.ruvector-extensionshas no CI publish workflow at all, ever — not even a glob match in any workflow file.Given that, I published this round by hand with the equivalent gates run locally in lieu of CI: full
cargo test -p ruvector-core(default features, clean) +cargo test -p ruvector-core --features lattice-embeddings(7/7 Lattice-specific tests pass, including the cross-provider prefix contract test),cargo publish --dry-run; and for the npm side, the actual full TS test suite viatsx(89 tests, 79 pass —npm test's plaintests/*.test.jsglob was silently only ever running 1 of 5 test files since 4 of them are.tsand never get compiled for that script),npm publish --dry-run.Recommend a follow-up to fix
release.yml's startup failure and add real CI publish coverage forruvector-extensions— flagging here rather than opening a separate issue since it's directly why this PR exists as a manual chore instead of a tag push.Co-Authored-By: claude-flow ruv@ruv.net