Repository navigation
v6.1.0
Highlights
- Find code by file path and identifier: a question about login attempt throttling now reaches LoginAttemptService.java with the default offline provider.
- Search up to 16 times faster: median search fell from 354 ms to 25 ms on a 21,546-chunk monorepo and from 202 ms to 15 ms on a 2,407-chunk repository.
- Rank better by default: local-hash nDCG@10 rose by up to 35% on code and documentation, and semantic models gained up to 3%.
- Upgrade without downtime: existing indexes keep answering while the next ingest rebuilds them.
What changed
- Ranking: BM25 leads local-hash fusion; hashed vectors only break ties and backfill.
- Keyword index: source paths and camelCase, acronym, and digit identifier parts join the full-text field, while embedded text stays unchanged.
- Search latency: candidate pools follow the reciprocal-rank fusion bound, abstention is evaluated lazily in ranked order, and ranking memoizes row keys.
- Storage: maintenance compacts tables from 64 small per-file fragments instead of waiting for 100,000 chunks.
- Upgrade: a lexical policy version keeps older indexes searchable, doctor reports readiness.lexicalIndexCurrent, and ingest or upgrade stages a validated rebuild.
- Dependencies: MCP SDK 1.31, mammoth 1.13, Astro 7.3.5 with @astrojs/react 7, and tooling updates; LanceDB stays on 0.30 so default installs keep the OpenAI and Transformers runtimes out.
- Release automation: npm trusted publishing replaces the stored npm token, so releases authenticate with the workflow's GitHub OIDC identity.
- Documentation: sharper READMEs with before-and-after benchmarks, plus updated configuration, CLI, migration, and release guides.
Verification
- pnpm validate, pnpm offline:smoke, and the GitHub quality, commitlint, and code analysis checks.
- Benchmarks on three code and documentation corpora with e5, mxbai, and local-hash: rankings equal or better, median search latency 13 to 16 times lower.
- Browser check of the English and French landing pages after the React integration update.
- Release checks pass with the job's OIDC identity, and a semantic-release dry run computed 6.1.0.
- Release assets include the Core tarball, checksums, an SBOM, and the release manifest
- The protected npm workflow requires publication with provenance
Install or upgrade
npm install --save-dev @jcode.labs/ragmir@6.1.0Requires Node.js 22.12 or later. Semantic embeddings use the separately installed optional Transformers package.
Full changelog: v6.0.1...v6.1.0