Repository navigation
v6.3.0
Highlights
- keep the index fresh in repositories that manage Git hooks with husky:
rgr hooks installnow adds the refresh to the.husky/<hook>scripts husky runs - tell agents in other projects exactly which folders a knowledge base serves when
mcpAllowedRootsrefuses them
What changed
- Git hooks: husky 9 (
.husky/_shims) and husky 8 (.huskywith_/husky.sh) are recognized; the Ragmir block goes into the tracked.husky/<hook>scripts instead of shims husky regenerates, reports carrymanager, and the CLI asks to commit the changed scripts; other tracked hooks folders still need--force - MCP: the
mcpAllowedRootsrefusal names the resolved folders instead of raw configuration values such as. - Documentation: both READMEs follow the conventions most successful open-source READMEs share, with a three-line quick start at the top, a community section, and downloads and stars badges; the CLI reference covers husky
Verification
- pass pnpm validate with 542 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 feature pull request
- install the hooks through husky 9 in a real product monorepo, and refuse an unrelated workspace on a real umbrella knowledge base configured with
mcpAllowedRoots - 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.3.0Requires Node.js 22.12 or later. Semantic embeddings use the separately installed optional Transformers package.
Full changelog: v6.2.1...v6.3.0