Skip to content

0.2.1 — upload guard fixes

Choose a tag to compare

View all tags
@Samuel-wei Samuel-wei released this 26 Sep 04:48
0.2.1
1f2f1b9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Fixes two upload bugs found by the end-to-end test run against production.

Fixed

  • Emptying or cutting a note is now held for review. The safety check that holds a note which suddenly becomes empty, or shrinks by more than 80%, measured the whole file, properties included. On a short note, the properties alone kept a wiped body above both thresholds, so the wipe was uploaded. The check now measures the note's body. The first edit after upgrading only checks for an empty body; the shrink check starts working again after the next upload.
  • Reordering properties no longer re-uploads the note. If you only changed the order of keys in the Properties panel, the note was sent again and re-processed on the server. That no longer happens. Changing a value, or reformatting it (for example quoting a value), still counts as an edit.

Nothing else changed. minAppVersion stays 1.11.4, and the plugin is still desktop-only.

Upgrading

From 0.2.0 or 0.1.1: replace main.js and manifest.json in <vault>/.obsidian/plugins/javis-wiki-sync/ and reload Obsidian. Your notes, settings and sign-in are untouched.

Coming from 0.1.1? This is the first Latest release with upload your own notes (off by default; nothing is uploaded until you pick a folder). See the 0.2.0 notes and the README for what is sent and how removal works.

Tested

The end-to-end runbook was run against the production server in a real Obsidian vault: 43 cases passed, none failed. Two were not run: one needs a staging server (a bad LLM key), the other a second Mac syncing the same vault through iCloud.

Assets 4
Loading