Skip to content

release: e-means consumers (ruvector 0.3.25, @ruvector/core 0.1.39, @ruvector/all 0.1.3, ruvector-core 2.5.2, ruvector-pq-search 2.3.1, ruvector-rairs 0.1.1) - #1491

Merged
ruvnet merged 1 commit into
mainfrom
release/e-means-consumers
Nov 11, 2026
Merged

ruvnet merged 1 commit into
mainfrom
release/e-means-consumers

Conversation

@ruvnet

@ruvnet ruvnet commented Nov 11, 2026

Copy link
Copy Markdown
Owner

Version bumps that ship #1489's clustering subpaths and training APIs. Both leaves are already published: ruvector-e-means 0.1.0 on crates.io and @ruvector/e-means 0.1.0 on npm.

Changes

  • npm: ruvector 0.3.25, @ruvector/core 0.1.39, @ruvector/all 0.1.3.
  • crates: ruvector-core 2.5.2, ruvector-pq-search 2.3.1 (explicit version, workspace stays 2.3.0), ruvector-rairs 0.1.1. Cargo.lock updates only these three.
  • @ruvector/all: feat: add shared e-means clustering and ecosystem integrations #1489 broke two umbrella tests (files list, manifest/dependency parity). e-means is now an ESM member (all.loadEMeans()), with d.ts and README rows, and the range check accepts exact pins for new 0.x edges.
  • ruvector: test/rabitq-optional.js guards the hard-dependency list. It now includes @ruvector/e-means, the deliberate edge feat: add shared e-means clustering and ecosystem integrations #1489 added for ruvector/clustering.mjs.

Other unreleased changes these releases carry

Validation (local)

  • cargo test -p ruvector-core -p ruvector-pq-search -p ruvector-rairs: all pass (290 core lib tests).
  • @ruvector/core test.js and test-retrieval.js pass. The clustering subpath runs.
  • @ruvector/all: 9/9.
  • ruvector: full npm test chain passes, including test/e-means.mjs.
  • Native: the ruvector-core-linux-{arm64,x64}-gnu 0.1.35 binaries that core 0.1.39 pins: arm64 LDAPR 0, max GLIBC_2.34.

@ruvector/wasm (tree 0.2.2 against 0.2.1 published) is intentionally not released here.

🤖 Generated with claude-flow

… ruvector-core 2.5.2, ruvector-pq-search 2.3.1, ruvector-rairs 0.1.1

Ships the e-means clustering subpaths and training APIs from #1489, now that
ruvector-e-means 0.1.0 and @ruvector/e-means 0.1.0 are published.

@ruvector/all: #1489 added @ruvector/e-means as a dependency and new files
without updating the umbrella's manifest test, so two tests failed. e-means
is now an ESM member (all.loadEMeans()), and the test accepts exact pins for
new 0.x edges alongside caret ranges.

ruvector: test/rabitq-optional.js guards the hard-dependency list; it now lists
@ruvector/e-means, the deliberate edge #1489 added for ruvector/clustering.mjs.

Unreleased changes also shipped by the crate bumps:
- ruvector-core: generated-ID reservation, live HNSW identity retention,
  memory batch validation (each with tests), fuzz lockfile refresh.
- ruvector-pq-search: Rust 1.88 MSRV fallback in codebook.rs.
- ruvector-rairs: clippy allowance, crates.io keyword length fix.

Co-Authored-By: claude-flow <ruv@ruv.net>
@ruvnet

ruvnet commented Nov 11, 2026

Copy link
Copy Markdown
Owner Author

Main-red evidence: 72 pass, 4 skipped, 1 fail. The only red job is cargo deny, with the single error[unsound] (xattr) that main's latest supply-chain run 43031735623 also has (#1487).

🤖 Generated with claude-flow

@ruvnet
ruvnet merged commit 74b8207 into main Nov 11, 2026
76 of 77 checks passed
ruvnet added a commit that referenced this pull request Nov 13, 2026
…ayer/perturb/learn (#1503)

* feat(ruvector): make @ruvector/weight-space a hard dependency (ADR-358 amendment)

Promote @ruvector/weight-space from an exact-pinned optional peer to an exact-pinned
runtime dependency, as @ruvector/e-means was. It stays lazy-loaded, so start-up is
unchanged, and a pruned install still degrades to the install hint.

- package.json: dependencies, removed from peerDependencies(+Meta)
- tests: manifest assertion flipped; weight-space-cli fails instead of skipping
- CI: drop the pack-and-install workaround now that the package is on npm
- README/ADR-358: reword; document that ruv-fann now arrives transitively, so
  neural-q uses its MLP backend by default on npm installs
- version bump left to the release PR, as in #1491

* feat(ruvector): weights set-layer, perturb and learn (CLI + MCP)

Expose the registry's versioned edit and fine-tune operations. Each writes a child
snapshot and never changes its parent.

- ruvector weights set-layer|perturb|learn; MCP weights_set_layer|weights_perturb|weights_learn
- new bin/weights-edit.js (shared plumbing injected from weights.js, no circular import)
- bounded inputs (epochs, rows, vector/patch sizes, seeds); file inputs confined to the
  working directory like save; a fine-tune that misses its held-out check writes nothing
  and returns accepted:false rather than an error
- test/weight-space-edit.js (10 tests, real package), wired into npm test and CI
- README + ADR-358 amendment; RUVECTOR_MCP_DENY verified to hide the write tools

* test(ruvector): allow @ruvector/weight-space in the hard-dependency guard
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant