Release v2.1.0
Indexly v2.1.0 adds safe FTS5 search-index deletion with clear-search, improves search behavior, and updates maintenance documentation.
Release v2.1.0 (2026-05-09)
Indexly v2.1.0 introduces safe search-index deletion with indexly clear-search.
The command removes rows from fts_index.db without deleting source files and includes dry-run previews, confirmations, cache handling, and audit logging.
Highlights
clear-search --path PATHremoves exact, prefix, or basename-matched search index rows.clear-search --tag TAG [TAG ...]removes files matching any listed tag.clear-search --allclears the full search index before a rebuild.--dry-runpreviews all modes without database changes.--yessupports safe automation for path, tag, and full-index cleanup.- Operation IDs connect the deletion plan, NDJSON logs, and final summary.
Search Improvements
- Lowercase words such as
and,or,not, andnearare treated as literal search text unless uppercase FTS operators are used. - Search results can be sorted by relevance, newest, oldest, or path.
- Tag statistics and search maintenance feedback are clearer.
Fixes And Reliability
- Cache invalidation failures during
clear-searchare warnings rather than confusing post-delete hard failures. - Database errors during search-index cleanup now include recovery hints such as
indexly doctorandindexly update-db. - Cleaned-data deletion handles basename, source path, and normalized full-path variants more robustly.
- Debug table inspection uses the expected database connection behavior.
Documentation
- Added Clear Search Results Safely.
- Updated the usage guide, search guide, developer guide, FAQ data, database design notes, and changelog.
Breaking Changes
None expected.
Contributors
- N. K. Franklin-Gent
- OpenAI Codex