Repository navigation
v6.12.2
Highlights
rgr init, doctor, and ingest hints suggest commands that run where Ragmir runs:rgrin the official Docker image and global installs, and the pinnednpx --yes @jcode.labs/ragmirin Python projects and other folders without an npm install of Ragmir.- OCR commands written by
rgr ocr setupin such a folder run at ingest time instead of failing.
What changed
- Core: without the generated runner or a project install, Ragmir suggested
pnpm exec rgr, which fails there, andnpx rgrasks npm for a package namedrgr. Projects that install or declare@jcode.labs/ragmir, monorepo apps under an installing root, and projects with the runner keep their current commands. - Tests: the pinned command, npm's global folder next to Node.js, a parent node_modules install, and a declared dependency.
Verification
- pass the full Core suite, types, Biome, knip, and the smoke tests
- pass in node:22-bookworm-slim: a global install suggests
rgr ingest,rgr doctor, andrgr search, and an npx run suggests the pinned release - pass a Docker check of 6.12.1 (slim and full images, Python client over the Docker MCP server) whose only failure was the
pnpm exec rgrhint this release fixes - pass CI on Linux, macOS, and Windows, Python 3.11 and 3.14, and CodeQL
- 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.12.2Requires Node.js 22.12 or later. Semantic embeddings use the separately installed optional Transformers package.
Full changelog: v6.12.1...v6.12.2