Skip to content

v6.3.0

Choose a tag to compare

@github-actions github-actions released this 27 Oct 17:14
· 6 commits to main since this release
e66b8e9

Highlights

  • keep the index fresh in repositories that manage Git hooks with husky: rgr hooks install now adds the refresh to the .husky/<hook> scripts husky runs
  • tell agents in other projects exactly which folders a knowledge base serves when mcpAllowedRoots refuses them

What changed

  • Git hooks: husky 9 (.husky/_ shims) and husky 8 (.husky with _/husky.sh) are recognized; the Ragmir block goes into the tracked .husky/<hook> scripts instead of shims husky regenerates, reports carry manager, and the CLI asks to commit the changed scripts; other tracked hooks folders still need --force
  • MCP: the mcpAllowedRoots refusal 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.0

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

Core on npm · Migration guide

Full changelog: v6.2.1...v6.3.0