joplin-plugin-incremental-backup 1.0.2 → 1.0.3

package/README.md

@@ -12,7 +12,7 @@ Each snapshot is a complete, self-contained copy of your data. Consecutive snaps
 - **Deduplication** — files that are byte-identical to the previous snapshot are stored as hardlinks instead of copies. Changed and new files are stored normally, so every snapshot remains complete on its own.
 - **Content-addressed matching** — files are matched by SHA-256 hash, so even renamed or moved notes don't consume extra space.
 - **Retention pruning** — keeps a configurable number of snapshots (default: 5) and automatically deletes the oldest ones. Deleting an old snapshot never damages newer ones, because hardlinked files are only removed when no snapshot references them.
-- **Skip unchanged backups** — if no note has been modified since the last snapshot, the backup is skipped entirely (can be disabled).
+- **Skip unchanged backups** — if nothing has changed since the last snapshot (notes, attachments, notebooks, tags, or which notes carry which tags), the backup is skipped entirely (can be disabled).
 - **Integrity verification** — every snapshot includes a `manifest.json` with the size and SHA-256 hash of every file. A verify command re-checks the whole snapshot and reports any missing or corrupted files.
 - **Crash-safe** — each backup run stages its files in a unique temporary directory (e.g. `_joplin_active_20261021T090000_12345_abcdef`) that is atomically renamed into place when complete. An exclusive lock prevents overlapping runs; the lock's mtime is refreshed periodically so a long export is never mistaken for an abandoned one. Stale locks are recovered atomically (rename-steal), and leftover staging data is cleaned up on startup unless another backup holds a fresh lock.
 - **Disk-space pre-flight** — checks available space before starting a backup and aborts the run if the backup drive is below the minimum free-space threshold, so a full disk can't produce a truncated snapshot. (If free space can't be measured on a platform, the backup proceeds with a warning.)
@@ -21,7 +21,6 @@ Each snapshot is a complete, self-contained copy of your data. Consecutive snaps
 - **Copy-mode warning** — if a previous snapshot exists but the filesystem doesn't support hardlinks (so every file had to be copied), a warning is shown so you know each snapshot consumes the full vault size.
 - **Durable metadata** — `manifest.json` and `latest.txt` are fsynced before and after the atomic rename, and a best-effort directory fsync is attempted so a power cut can't corrupt the snapshot index. Exported files themselves are left to OS writeback; fsyncing 20 k files per backup would be prohibitive.
 
-
 ## How to use
 
 1. Install the plugin and open **Tools > Options > Incremental Backup**.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "joplin-plugin-incremental-backup",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "scripts": {
     "dist": "webpack --env joplin-plugin-config=buildMain && webpack --env joplin-plugin-config=buildExtraScripts && webpack --env joplin-plugin-config=createArchive",
     "prepare": "npm run dist",

package/publish/io.github.raytray.joplin-incremental-backup.json

@@ -2,7 +2,7 @@
 	"manifest_version": 1,
 	"id": "io.github.raytray.joplin-incremental-backup",
 	"app_min_version": "3.7",
-	"version": "1.0.2",
+	"version": "1.0.3",
 	"name": "Incremental Backup",
 	"description": "Deduplicated incremental snapshots of your Joplin data using the native Raw export format.",
 	"author": "raytray",
@@ -11,8 +11,8 @@
 	"keywords": [
 		"backup"
 	],
-	"platform": [
-		"deskop"
+	"platforms": [
+		"desktop"
 	],
 	"categories": [
 		"files"
@@ -20,6 +20,6 @@
 	"screenshots": [],
 	"icons": {},
 	"promo_tile": {},
-	"_publish_hash": "sha256:ac4f78b1972925a5b3b55d0da17827f748d6a195ba187a2f2c2ca8a29d2607ee",
-	"_publish_commit": "main:8a71e1debc8d2fd1e1ed14deb75efcfeb31bc006"
+	"_publish_hash": "sha256:cfeee5c68acb2a7ddf31f3f1981dea03ff960cefde01932ef16ccaedc48611d2",
+	"_publish_commit": "main:24c6b70de862802fe79d3c67b2afa903b4662630"
 }