Repository navigation
v6.2.1
Highlights
- keep indexing reliable on Windows machines where antivirus, search indexing, or sync clients such as OneDrive briefly hold new files
What changed
- Windows reliability: manifest, state, cache, config, model, and lock-owner writes retry the transient EPERM, EACCES, and EBUSY renames that Windows reports while another process holds a file, for about two seconds, and directory removals retry busy or not-yet-empty directories; other platforms and other errors behave as before
- Tests: integration test timeouts scale by the factor measured on Windows runners, where spawning git, fsync, and small-file churn cost 9 to 16 times more than on Linux
- Documentation: the troubleshooting guide explains what to do if Windows still reports EPERM, EBUSY, or ENOTEMPTY
Verification
- pass pnpm validate with 540 Core tests and 24 landing tests plus coverage, API, CLI and MCP smoke, builds, packaging, license policy and release smoke checks
- pass Quality gate, Linux x64, macOS ARM64 and Windows x64 portability, Commitlint and CodeQL analysis on the fix pull request
- measure Windows and Linux runners side by side: a demo ingest takes 409 ms against 147 ms and a warm search 23.5 ms against 14.8 ms, in line with the operating system's process and file costs
- 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.2.1Requires Node.js 22.12 or later. Semantic embeddings use the separately installed optional Transformers package.
Full changelog: v6.2.0...v6.2.1