Jev Graph Search 0.2.2

Jev Graph Search is now published as jev-graph-search, with its repository at Emlembow/jev-graph-search and CLI command jev-graph-search.

Install the pinned package with npm install --global jev-graph-search@0.2.2, or run npx --yes --package=jev-graph-search@0.2.2 jev-graph-search --help.

Existing credentials and cache locations remain compatible, including the jevgraph configuration directory and JEVGRAPH_* environment names. The agent skill is now named jev-graph-search. Local Markdown, Obsidian, and Logseq Markdown graph behavior is unchanged. The package is now released under the MIT license.

Version 0.2.1 bootstrapped the new package name through an authenticated local publish. Version 0.2.2 uses the trusted GitHub publication workflow with npm provenance. The previous package remains available and receives a migration notice after the replacement passes verification.

Jevgraph 0.2.0

Jevgraph now focuses on local Markdown knowledge graphs, with direct folder support for Obsidian vaults and Logseq Markdown pages and journals. No backup or export step is required.

• Reads common YAML aliases/tags and Logseq page properties; aliases participate in retrieval and bounded semantic scoring.
• Keeps graph evidence and original passages, and excludes detected Logseq metadata and backup folders.
• Retains optional JSON graph exchange, offline inspection, and private no-clobber output.
• Breaking change: removes the remote workspace integration and its CLI/API surfaces. Logseq database and Org-mode formats remain unsupported.

Validated with 93 synthetic and isolated regression tests. The trusted GitHub Actions workflow publishes the npm package and requests provenance.

Jevgraph 0.1.1

JSON exports now create private files without overwriting existing paths, and Notion endpoints require HTTPS except for explicit local tests. The bundled skill clarifies untrusted source content, bounded provider transfers, and private snapshot handling.

Installation instructions pin jevgraph@0.1.1. This release triggers the configured npm trusted-publishing workflow with provenance.

Validation: 96 isolated runtime/security tests passed before the version-only runtime update; the final candidate passed version, audit, offline-search, and package-content checks.