Skip to content

Releases

v6.15.2

Choose a tag to compare

@github-actions github-actions released this 16 Nov 14:46
a27c43a

Highlights

  • the published Ragmir package presents only the Ragmir name, and the migration note names only the jcode-works/ragmir repository
  • the README and the npm README describe the new social card

What changed

  • Core: ensureRagmirGitignore recognizes the Ragmir block header by its shape, a comment that ends with "Ragmir", which keeps reusing the prefixed header earlier releases wrote
  • Docs: the migration note says the previous repository URLs redirect without naming them
  • Landing: the social card shows the current message in Inter 900 on the site's dot field, and its alternatives describe it

Verification

  • pass the CI of pull requests 298, 300, and 301, including the new gitignore tests
  • pass pnpm commitlint and verifyRelease on this commit
  • 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.15.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.15.1...v6.15.2

v6.15.1

Choose a tag to compare

@github-actions github-actions released this 16 Nov 12:44
901f1c1

Highlights

  • Ragmir now lives at github.com/jcode-works/ragmir; GitHub redirects the old URLs, so existing installs, plugin marketplaces, and clones keep working
  • the install section of ragmir.com now sits on the same animated dot field as the agent section

What changed

  • Repository: every link, install command, badge, and manifest names jcode-works/ragmir: the READMEs and guides, llms.txt, the Claude Code, Codex, Cursor, Gemini CLI, and Qwen Code plugins, the Agent Skills, the Context7 and skills.sh links, server.json, and the Docker labels
  • Packages: npm and PyPI metadata point to the new repository; package names do not change
  • Release: the npm and PyPI trusted publishers, the release notes, and the wiki sync use the ragmir repository, and the migration guide documents the move
  • Landing: an animated dot field behind section 002 (Install), hydrated when visible and static under reduced motion

Verification

  • pass pnpm validate and pnpm python:check on the release tree
  • pass the CI of pull request 295 on develop
  • verify the staging landing in a browser at desktop and mobile widths
  • 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.15.1

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

Core on npm · Migration guide

Full changelog: v6.15.0...v6.15.1

v6.15.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 17:50
97c5cd8

Highlights

  • Ragmir indexes XMind mind maps, cited sheet by sheet with their topics, notes, markers, links, and relationships.
  • 238 more file types index out of the box, 906 in all: C++ modules, Perl modules, Gherkin and Robot Framework tests, XSLT, Phoenix templates, MSBuild and WiX projects, shaders, Nextflow and Snakemake workflows, CodeQL and YARA rules, systemd and Podman units, DITA, man pages, CITATION.cff, and more.
  • Terraform state and variable files and the Firebase GoogleService-Info.plist are treated as secrets and never indexed.

What changed

  • Mind maps: XMind 8 and XMind 2020 or later maps give one section per sheet with the topic outline, notes, labels, task and priority markers, web links, floating, callout, and summary topics, and labelled relationships; a password-protected map fails with a readable error.
  • Formats: an inventory against GitHub Linguist added extensions of popular languages and common tool files, all as text with line citations, while extensions shared with common binary formats stay out. XML property lists index with line citations, a binary one fails with the plutil command that saves an XML copy, and binary .xlsb workbooks get export advice.
  • Security: .tfstate, .tfvars, and GoogleService-Info.plist are skipped as sensitive files, even when includeExtensions names them.
  • Retrieval: C++ modules and secondary JavaScript, Java, C#, Python, and Ruby extensions get the code definition boost; ronn and mdsvex files keep Markdown heading paths.
  • Documentation: the formats, configuration, and migration guides, the README, llms.txt, Context7 rules, the setup skill, and the landing list and FAQ show the new families and counts.

Verification

  • pnpm validate and pnpm python:check on the release tree.
  • pnpm --filter @jcode.labs/ragmir test: 67 files, 666 tests passed.
  • The pull request CI on develop and main: Quality gate, Commitlint, and Analyze TypeScript.
  • 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.15.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.14.0...v6.15.0

v6.14.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 16:22
c43f1d0

Highlights

  • Agents can tell which variables a service needs: .env.example and other dotenv templates index their names and comments, with every value masked; real .env files stay skipped.
  • Templates such as env.example no longer keep their values in the index: the next ingest rebuilds without them.
  • The ragmir skill names the command to run in a project without an npm install or in Docker.

What changed

  • Formats: dotenv templates (example, exemple, sample, template, or dist after .env, env, or *.env) keep each name and comment on its own line, so line citations stay exact; quoted multi-line values, token-shaped strings and JWTs in comments, and other lines are dropped.
  • Security: templates named without a leading .env. were indexed with their values through their extension; parser version 6 stages a validated rebuild without them, and the configuration guide lists the credential files that are always skipped.
  • Skills: the ragmir skill points to the pinned npx command or rgr in the Docker image when a project has neither an npm install nor the generated runner.

Verification

  • pass the formats, files, supported formats doc, parsing, ingest, index policy, upgrade, preview, security, and skill tests, including a template with a key, a URL password, and a private key
  • pass public smoke with its secret scanner, types, Biome, and knip
  • 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.14.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.13.0...v6.14.0

v6.13.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 15:26
1646725

Highlights

  • Index HAR captures saved from browser DevTools, Charles, Proxyman, or Fiddler: each API or page request is cited on its own, with cookies, credentials, and tokens left out.
  • Ragmir is published under JCode Works on npm and PyPI.

What changed

  • Formats: .har files index as an overview plus one section per request with its method, URL, status, query parameters, headers, and text bodies; identical repeated requests count once, and static assets and CORS preflights are skipped.
  • Safety: cookies are never read; authorization headers, API keys, tokens, passwords, sessions, signatures, OAuth codes and states, URL credentials, JWTs, and bearer values become "(value omitted)"; a .har file that is not an HTTP Archive fails instead of being indexed raw.
  • Publishing: the npm and PyPI packages, plugin marketplaces, and citation metadata name JCode Works (contact@jcode.works) as author, and the landing credits the organization.
  • Maintenance: pnpm wiki:sync copies the guides into the GitHub wiki, and the release checklist adds the wiki sync and a Context7 refresh.

Verification

  • pass the formats, supported formats doc, files, parsing, preview, and ingest tests, including a HAR fixture with every kind of secret above
  • pass the built CLI on a Firefox HAR: cited search, empty stderr, no secret in the preview
  • 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.13.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.12.2...v6.13.0

v6.12.2

Choose a tag to compare

@github-actions github-actions released this 15 Nov 12:33
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

v6.12.1

Choose a tag to compare

@github-actions github-actions released this 15 Nov 11:56
73fb8d4

Highlights

  • The first rgr ingest and every rgr ingest --rebuild print nothing on stderr, so a new project starts clean and agents can parse rgr ingest --json 2>&1.
  • The agent plugins for Claude Code, Codex, Cursor, Gemini CLI, and Qwen Code run 6.12.0 and its new file types.
  • The Python guide's terminal steps run in a Python project without a local npm install.

What changed

  • Core: a missing index table is created in LanceDB's create mode, so LanceDB no longer logs "No existing dataset ... it will be created" on the first ingest and on rebuilds. The root smoke test fails when the first index write prints LanceDB logs.
  • Plugins: the MCP launchers, /ragmir:index, the ragmir-index skill, GEMINI.md, and the agent guide pin @jcode.labs/ragmir@6.12.0; the plugin manifests move to 1.2.1 and the Gemini and Qwen extensions to 6.12.0.
  • Python guide: the terminal steps run npx @jcode.labs/ragmir, because npx rgr only resolves once a project installs the npm package.

Verification

  • pass the store, ingest, upgrade, generation retention, and client tests, types, Biome, the smoke tests, public smoke, and plugin validation
  • pass an end-to-end check of the published 6.12.0: CLI, TypeScript client, LangChain.js tools, MCP through the Python client, LangChain and LlamaIndex retrievers, plugin launcher, GHCR images
  • 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.1

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.0...v6.12.1

v6.12.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 11:25
2519b45

Highlights

  • Index Visual Studio projects and solutions, Godot scenes and scripts, and build manifests such as go.mod, meson.build, and PKGBUILD, with line citations and no extra install.
  • Cover every popular GitHub Linguist language: more than 650 extensions and file names.

What changed

  • Formats: .csproj, .fsproj, .vbproj, .props, .targets, .nuspec, and .sln; Godot .gd, .gdshader, .tscn, .tres, and project.godot; Luau, Lean, Agda, Idris, TLA+, Dafny, Vala, Nushell, ArkTS, Ballerina, Cadence, Carbon, Odin, KCL, Roc, Chapel, templ, Slint, KDL, HOCON, Avro IDL, and more, chosen from an inventory against GitHub Linguist.
  • Build files: go.mod, go.work, meson.build, configure.ac, PKGBUILD, APKBUILD, Kbuild, SConstruct, BUCK, Android.bp, cabal.project, dune-project, rebar.config, Puppetfile, cpanfile, firestore.rules, and tool dotfiles such as .rspec, .coveragerc, and .releaserc.
  • Safety: extensions shared with binary formats, secret-bearing dotfiles, and lockfiles stay out; existing types keep their extraction, so indexes need no rebuild.
  • Documentation: the supported formats guide, READMEs, llms.txt, Context7 rules, the setup skill, and the landing show the new families, and RELEASING.md makes the landing deployment reproducible.

Verification

  • pass formats, guide, and discovery tests, lint, knip, public smoke, and landing checks
  • 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.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.11.0...v6.12.0

v6.11.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 10:20
f67ce4e

Highlights

  • Index more than 450 file types, now including email and mailboxes and Figma, Sketch, Excalidraw, tldraw, Postman, Insomnia, and Evernote exports, each object cited on its own.
  • Let agents list documents, read them through, filter by glob, and refresh the index over MCP.
  • Use Ragmir natively from Python, LangChain, LangGraph, and LlamaIndex, and give LangChain.js agents cited search and expansion tools.
  • Run semantic search and local OCR without Node.js in the new full Docker image.
  • Install Ragmir skills for any coding agent from skills.sh.

What changed

  • Formats: MIME mail (.eml, .emlx, .mbox, .mhtml) with charset and encoded-word decoding; Figma .fig files and REST exports, Sketch, Excalidraw, tldraw, and JSON Canvas cited frame by frame; Postman and Insomnia requests with secret values omitted; Evernote, FictionBook, GeoJSON, and SARIF; Office macro and template variants, flat OpenDocument, and 300 more code, build, and configuration types. Existing indexes stage a validated rebuild on the next ingest.
  • MCP: ragmir_sources lists the indexed documents, ragmir_ingest refreshes the private index with progress, ragmir_expand pages through a whole document, path filters accept globs, an answer prompt requests fully cited answers, and refused searches point agents to ragmir_ingest.
  • LangChain.js: createRagmirTools and RagmirToolkit give LangChain and LangGraph agents ragmir_search and ragmir_expand tools that keep documents as artifacts.
  • Python: the ragmir client (sync and async), langchain-ragmir, and llama-index-retrievers-ragmir on PyPI drive the same engine through Node.js or Docker.
  • Docker: a full image adds the semantic runtime and Tesseract OCR; releases tag X.Y.Z, X.Y, and X with SBOM and provenance attestations, and the MCP Registry lists the image.
  • Skills: ragmir, ragmir-setup, ragmir-build, and ragmir-evaluate Agent Skills on skills.sh.
  • Fixes: rgr sources add keeps a committed source list when a local config exists, and the generated Codex helper registers the server per project.
  • Documentation: guides for Docker, Python, golden files, and support, and a shared Claude Code setup for contributors.

Verification

  • pass pnpm validate with 656 Core and 29 landing tests, and pnpm python:check with 43 tests
  • pass CI on Linux, macOS, and Windows, Python 3.11 and 3.14, and the Docker image smoke test
  • validate server.json, context7.json, and the Claude Code settings against their schemas
  • 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.11.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.10.0...v6.11.0

v6.10.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 06:18
199737d

Highlights

  • Data models, diagrams, process models, BI workbooks, and API descriptions are indexed object by object: an agent cites model.pdm:section=Table%20INVOICE instead of a line range of an export.
  • PowerDesigner, ERwin, MySQL Workbench, Oracle Data Modeler, draw.io, Visio, BPMN, DMN, ArchiMate, UML XMI, Tableau, OpenAPI, AsyncAPI, and Outlook .msg files are supported with no new install.
  • PL/SQL, Kotlin, Swift, Terraform, Protobuf, GraphQL, Prisma, DBML, PlantUML, TMDL, and other text formats are indexed by default with line citations.

What changed

  • Core: new section citation location; tables, entities, pages, decisions, and operations each become a cited section, with columns, keys, joins, flows, rules, and referencing objects.
  • Core: generic XML is recognised by its first bytes and otherwise keeps line citations; binary PowerDesigner models and damaged archives are reported per file without stopping ingestion.
  • Core: Outlook messages are read through a bounded Compound File reader; draw.io pages inflate within a 25 MB bound; one file yields at most 20,000 sections.
  • Core: the extraction policy moves to version 4, so the next ingest stages a validated rebuild.
  • Docs: new supported formats guide listing every extension, guarded by a test; README and llms.txt link it.
  • Landing: supported formats card, reworked team page with a jcode.works link, larger hero title on phones, edge-to-edge deploy and data-control sections, and a menu drawer that slides again.

Verification

  • pnpm validate: lint, knip, security audit, type check, Core and landing tests with coverage, build, API check, smoke, package check, release smokes, and release artifacts.
  • Structured format tests on synthetic fixtures, corrupted files, and an ingest with citations.
  • Ingest and search on a copy of real PowerDesigner CDM and PDM models and a PL/SQL package.
  • Staging landing checked in English and French on phone and desktop widths.
  • 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.10.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.9.0...v6.10.0