Highlights
Urmare 0.2.0 introduces persistent incremental indexing for faster repeated impact analysis.
What’s new
- Reuses a transactional local repository index between commands.
- Parses only changed files and updates affected relationships.
- Handles commits, staged changes, untracked files, deletions, and renames.
- Falls back to complete analysis whenever incremental correctness cannot be guaranteed.
- Adds extensive correctness, recovery, and incremental-update coverage.
Benchmark reference
- Across 15 paired samples on Flask, FastAPI, Django, pandas, and Apache Airflow, median warm end-to-end latency ranged from 75 ms to 256 ms. One-file incremental latency ranged from 79 ms to 263 ms.
- Every incremental run parsed one file, changed no graph edges, and matched fresh uncached analysis.
- See the complete benchmark methodology and results in peformance.md
- There are no intentional breaking changes to the CLI or JSON output.
Full Changelog: v0.1.1...v0.2.0