Skip to content

release: qualify reviewed e-means 0.1.1 and dependent integration fixes - #1490

Open
ruvnet wants to merge 27 commits into
mainfrom
release/e-means-leaf-0.1.0
Open

ruvnet wants to merge 27 commits into
mainfrom
release/e-means-leaf-0.1.0

Conversation

@ruvnet

@ruvnet ruvnet commented Nov 11, 2026 •

Copy link
Copy Markdown
Owner

Publish the reviewed shared e-means crate and npm runtime as 0.1.1, then unblock ruv-FANN #227.

Public npm 0.1.0 reproduced three failures in indexed IVF/PQ validation and codebook serialization when typed-array iterators were overridden. This change validates stored coordinates and adds actual Darwin tuning compatibility on Node 20.0.0. The externally published 0.1.0 archives remain immutable.

The release lane qualifies source and packed Cargo tests, an isolated audit, Rust 1.81, an archived-source WASM build, npm Node/Worker/Chromium/declaration/installed consumers, and the sealed package on Node 20.0.0. Fifty-five guards reject missing, skipped, forged or source-mismatched evidence. Publication is restricted to the protected workflow, followed by canonical registry-byte checks, fresh public consumers and redownload of every GitHub release asset.

Current immutable source: 0e2b1931eb49c4a29af4055996e82f3d7df892b3. Concurrent upstream #1489, #1491 and generated binaries through ed1d3fcf are preserved. Four npm facades temporarily retain public 0.1.0 pins to avoid installing unpublished dependencies; a separate promotion patch is prepared for after verified 0.1.1 publication. Upstream package versions and unrelated registry records are preserved.

Main-writing automation and the publisher share a job-level mutation queue. Binary jobs check their exact build SHA and reject stale, non-fast-forward writes.

Validation and current external blocker:

  • Original exact-source preflight: qualify passed; sealed artifact 13889029957 preserved and independently validated; required Node 20 job remains queued.
  • Its original sealed archive independently passed local Node 20.0.0/npm 9.6.4: 27 tests, zero failures/skips, plus real offline Darwin/WASM and declaration consumers. This diagnostic does not replace hosted qualification.
  • One full replacement preflight uses the unchanged commit on a new release branch. It remains queued. A replacement must pass both jobs and its own seal checks; evidence will not be mixed between runs.
  • GitHub status reported an Actions major outage at 20:48 UTC on November 11. Normal cancel, force-cancel and targeted retry rejected the original queued state. No gates were bypassed.
  • Same-source isolated npm CI remains queued. The unchanged isolated install passed locally on a fresh Node 20 cache, including the facade test; 55 release guards, 9 facade tests and 11 native adapter tests passed locally.

NOT READY: no 0.1.1 publication or main promotion has occurred. Both hosted preflight jobs must succeed before unchanged-source promotion and protected publication. #1487 tracks an existing broad monorepo supply-chain failure; isolated package qualification does not certify unrelated dependencies. No hosted Cloudflare deployment or live Vectorize write is claimed.

Reuven Cohen and others added 23 commits November 11, 2026 17:40
…add release metadata

- ruvector-core ProductQuantized::encode keeps the existing f32 ordering for
  finite distances; f64 is used only when an f32 squared distance overflows.
  Adds a regression test with a pair that ties in f32 but not in f64.
- Pin new 0.x edges exactly: rand_chacha =0.3.1, rand_core =0.6.4 and
  ruvector-e-means =0.1.0 in core, pq-search and rairs.
- @ruvector/core: e-means moves from optionalDependencies to dependencies,
  since clustering.mjs re-exports it statically and has no fallback.
- e-means MetaHarness accepts Darwin 0.13.0 and 0.13.1 (both run). ruvector
  resolves ^0.13.0 to 0.13.1, which made tuneClustering throw through
  ruvector/clustering. The receipt reports the version actually loaded.
- cloudflare/build imports esbuild lazily and explains a missing install.
- ADR-356 metadata for ruvector-e-means and @ruvector/e-means (homepage, bugs,
  keywords, description, animated SVG). READMEs no longer state unreleased
  ruv-FANN or consumer facades as available; crate README links are absolute.
- ADR-359 labels the author's speedups as measured against an earlier build
  that is not in the tree, and adds an independent reproduction of the
  pruning change with matching output digests.

Co-Authored-By: claude-flow <ruv@ruv.net>
@ruvnet ruvnet changed the title release: publish shared e-means before dependent integrations release: qualify reviewed e-means 0.1.1 and dependent integration fixes Nov 11, 2026

This branch has not been deployed

No deployments
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