Repository navigation
Releases
Releases · rush-db/obsidian-plugin
0.4.0
Minor Changes
- ef2afcf: Setup needs fewer steps: the API key is stored under the secret
rushdb-api-default(and the engine token underrushdb-engine-default) unless you pick another one, and a new install indexes the whole vault (/) once RushDB is connected. Saved settings are kept as they are. The related-notes sidebar now uses the RushDB logo, has a refresh button on each section that reloads just that section, shows how similar each similar note is (0.98), and lists notes with the most tags in common first, with a×Nbadge whose tooltip names the shared tags.
0.3.1
Patch Changes
- ce0681e: A resync walks only the folders chosen for indexing instead of listing every file in the vault, so paths outside them are never read. Dev tooling no longer pulls in a
minimatchversion with a security advisory.
0.3.0
Minor Changes
- 2554434: Requires Obsidian 1.13 or later (breaking for older versions). The settings tab moves to Obsidian's declarative settings, so every RushDB setting shows up in the settings search, and the API key and engine token are kept in Obsidian's secret storage instead of the plugin's data file; keys saved by earlier versions are moved there on first load.
0.2.1
Patch Changes
- 2e50eb9: Fix the directory review: opening the related-notes view no longer relies on an API newer than the declared minimum Obsidian version (1.5.0). Releases now carry GitHub artifact attestations for
main.js,styles.cssandmanifest.json, and the test toolchain is updated past its security advisories.
0.2.0
Minor Changes
- 2ad86ed: Sync large vaults smoothly: notes are sent in batches of up to 100 (about 1 MB per request), deletions in bulk, and links as one request per 500 notes (each note's new
linksToproperty lists the vault-qualified keys of the notes it links to and is joined to their newlinkKey, so links never cross vaults that share a project; link relationships carrykind: "wikilink"). Notes synced by 0.1.0 are re-sent once in the new format, and progress is saved after every batch so an interrupted first sync resumes where it stopped. Resyncs list only ids, paths and hashes instead of downloading every note's text, and requests are retried with backoff, which also rides out rate limits.