Skip to content

v6.12.2

Choose a tag to compare

@github-actions github-actions released this 15 Nov 12:33
· 28 commits to main since this release
51c0b24

Highlights

  • rgr init, doctor, and ingest hints suggest commands that run where Ragmir runs: rgr in the official Docker image and global installs, and the pinned npx --yes @jcode.labs/ragmir in Python projects and other folders without an npm install of Ragmir.
  • OCR commands written by rgr ocr setup in 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, and npx rgr asks npm for a package named rgr. 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, and rgr 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 rgr hint 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.2

Requires Node.js 22.12 or later. Semantic embeddings use the separately installed optional Transformers package.

Core on npm · Migration guide

Full changelog: v6.12.1...v6.12.2