Release Notes

2.5.0 (2026-10-22)

Features

  • plugin: always write a PDF-backed document’s original and annotated copy
  • plugin: annotate PDFs locked with an owner password

Bug Fixes

  • plugin: keep a locked source’s trailer in the annotated copy
  • plugin: map an older format 1 PDF without redirectionPageMap page by page
  • plugin: map format 1 PDF layers through redirectionPageMap
  • plugin: never draw a text highlight or highlighter stroke in a dark colour
  • plugin: only swap near-black highlight colours for yellow
  • plugin: read a palette text highlight by its palette colour
  • plugin: report ink that matched no source page

2.4.1 (2026-10-22)

Bug Fixes

  • settings: handle a cleared device token secret picker

Reverts

  • Revert “chore(deps-dev): bump conventional-changelog-conventionalcommits”

2.4.0 (2026-10-03)

Improved

  • Your reMarkable credentials no longer travel with your vault. The device token now lives in Obsidian’s secret storage, on each device, instead of in the plugin’s data file, which is synced along with your vault by Obsidian Sync, Git, Syncthing or a cloud folder. The data file only keeps the name of the secret.
  • Nothing to do when you update. Every device moves the token into its own secret storage the next time it starts, so you stay connected on all of them. The old plain-text copy is kept in the data file for 60 days so the devices you open less often can migrate too, and is then removed automatically. Once all your devices run this version, you can remove it right away with Settings → Remarkable Synchronizer → Remove plain-text copy now.
  • A clear message on a device that has no token. If a device starts after the plain-text copy is gone and has never migrated, the plugin says the vault is paired, but not on this device, instead of failing. Connect once on that device; your other devices stay connected.

2.3.0 (2026-10-01)

Improved

  • A notebook that keeps failing no longer drains automatic sync. Automatic sync used to download it again on every run, without telling you. Now it retries less often each time (up to every 16 runs), and tells you once, with the reason, after the second failure in a row. It tries again right away when the notebook changes on your device, and syncing it from the panel always tries immediately.
  • One unreadable notebook no longer blocks cleanup. If the reMarkable cloud cannot serve one item, the plugin still forgets notebooks you deleted on the device, and stops asking the cloud for that item until it changes.
  • Quieter warning for the same unreadable items. When a refresh cannot read the same items as the previous one, the panel shows a short muted note instead of the red banner.

Fixed

  • A notebook whose cloud index listed one of its files twice failed to download on every sync.

2.2.1 (2026-10-01)

Fixed

  • Syncing works again for accounts on the newer reMarkable cloud format. Since 2.2.0, these accounts saw “1 item(s) could not be read from the reMarkable cloud”, and every notebook failed to download. The plugin read a header line of the cloud’s index as if it were a file. (#44, #45)

Maintenance

  • Updated dependencies and build tooling.

2.2.0 (2026-09-28)

Sync you can trust

  • Edited notebooks are picked up again. A notebook you changed on the device after its first sync could stay marked as synced forever, so automatic sync skipped it. Sync now compares the cloud’s own timestamps, so edits are detected. After updating, notebooks you edited since their last sync will all show “Needs sync” at once: that is real work catching up, not a new bug.
  • Untouched notebooks are no longer downloaded again and again. A failed or partial cloud listing (offline, a timeout, a rate limit) used to erase the plugin’s sync state, and the next run downloaded your whole library again. The state is now only cleaned up after a complete listing.
  • Notes no longer land in a shorter folder path when a folder cannot be read. When the cloud could not return a folder’s details, its notebooks could be written to a shorter path, then to the right one on the next sync, leaving a copy behind. Such notebooks are now held back until their folder can be read.
  • A notebook is only marked synced when every file arrived. A download with missing pages now fails instead of being processed with pages absent.

Kinder to large accounts and flaky connections

  • At most 6 requests run at once per listing or download, rate limits and server errors are retried with backoff, and an outage now stops the sync quickly instead of retrying for a long time.
  • The sidebar keeps showing your last known notebooks when a refresh fails or is partial. The ones it could not refresh are greyed out and cannot be synced until a refresh succeeds, and a banner says what happened.
  • Messages say what went wrong: “reconnect” when the reMarkable cloud refuses your device’s credentials, “try again later” when it could not be reached.

Safer files in your vault

  • The highlights note’s link to the annotated PDF now works for notebook names containing [, ], | or ^ (a name that also contains # or : is shown as plain text instead of a link).
  • The target folder is checked in the settings (no absolute paths, .. or characters other systems reject), and a hand-edited value is kept inside the vault on load.
  • A folder or file already sitting where the plugin wants to write now produces a clear error naming the path.
  • The documentation now warns that generated files are overwritten when their notebook syncs again: annotate on the device, or rename a file to keep your edits (the plugin then recreates the original next to it).

Thanks

Many of these fixes come from delize’s careful reports and patches.

2.1.0 (2026-09-17)

Features

  • build: fail the build on a lockfile the catalog review cannot parse
  • build: make the rule floor check that it is still wired in
  • build: refuse commits that loosen the rules instead of fixing the finding
  • parser: render images placed by the capture tool

Bug Fixes

  • build: exclude bun-types alongside @types/bun from the release-age gate
  • deps: move the fast-uri override off the vulnerable line
  • deps: move the js-yaml override off the vulnerable line

2.0.0 (2026-08-29)

⚠ BREAKING CHANGES

  • plugin: minAppVersion moves from 1.8.7 to 1.13.0 — the declarative settings API (getSettingDefinitions) only exists there.

getSettingDefinitions() replaces the display() tab and its eight section renderers wholesale. The per-section redisplay callbacks are dead under this API (display() never runs), so the connect/disconnect flows, the legacy-token removal and every visibility-affecting write now re-render through update() instead. The conditional rows (server URL, cloud-change warning, sync interval, image quality) declare visible: hooks over live state; the connection status row renders both its description and its Connect/Disconnect button from live state; the cloud-change warning is an info row with the mandatory no-op render hook (definitions with neither control nor render are skipped entirely).

updateSettings is now persist-then-commit INSIDE the same write queue as the token writes: the produce() derives from the previously committed state, the merged data.json (settings plus sibling token entries) is saved first, and memory is swapped only after the write lands — a settings save can no longer clobber a concurrent token refresh, and the old commit-before-save ordering is gone. setControlValue rejects type mismatches, non-finite/out-of-range numbers, out-of-enum dropdown values and unknown keys; an invalid rmfakecloud URL is now refused with the framework’s inline error where the old tab painted an error span but persisted the value anyway.

9 new tests cover the write path — persist-then-commit ordering and write serialization are mutation-checked (deliberately regressed implementations fail them) and the token-preservation property is asserted against the merged write. 482 tests, tsc, lint –max-warnings 0 and build green; the prefer-setting-definitions advisory from the previous commit is now satisfied.

Features

  • plugin: declare the settings tab (Obsidian 1.13 declarative settings)

Bug Fixes

  • build: align with the catalog reviewer’s archive, ruleset and audit
  • build: harden the release path after adversarial review

1.16.0 (2026-08-20)

Features

  • domain: scale ink per device across all five models
  • highlights: parse text highlights and embed them in the PDF
  • output: add a deterministic PDF writer
  • output: burn annotations back onto source PDFs
  • output: write one PDF per notebook behind a save-as-PDF toggle
  • parser: extract typed text into a note
  • parser: read the colour a glyph range carries, closes #acff85
  • renderer: read per-stroke colour, opacity and fixed nib widths
  • settings: make the highlights note opt-in

Bug Fixes

  • domain: give the shading marker its real width
  • domain: take pen colours and widths from the reference renderer
  • output: safe highlight text encoding and correct rotated-page mapping
  • output: skip vault writes when the bytes are unchanged
  • output: write EPUB sources under their own extension
  • output: write unannotated sources, stop buffering unused pages, surface failures
  • parser: correct the typed text layout against a real notebook
  • parser: order typed text per position so mid-run insertions survive
  • pdf: give highlight annotations an explicit appearance stream, closes #acff85
  • pdf: place pages at their physical size, not a fixed 1872 units
  • renderer: highlighter compositing and typed-only pages
  • renderer: map the newer firmware stroke colours
  • renderer: port the real per-pen width response
  • settings: stop savePdf resetting to false on every restart
  • settings: validate constrained values on load

1.15.0 (2026-08-12)

Features

  • panel: sort notebooks within each folder (#15)

Bug Fixes

  • panel: render icon buttons on mobile
  • plugin: stop shipping Tailwind Preflight in the stylesheet #19 #19
  • renderer: map the stroke colours newer firmware emits (#14)

1.14.0 (2026-07-30)

Features

  • plugin: enable experimental mobile support
  • plugin: replace JSZip with fflate for .rmdoc extraction

Bug Fixes

  • plugin: generate the device id without crypto.randomUUID

1.13.0 (2026-07-30)

Features

  • plugin: show what’s new in a tab instead of a modal dialog
  • plugin: store reMarkable tokens in plugin data
  • plugin: surface support CTAs everywhere users can see them

1.12.0 (2026-07-29)

Features

  • plugin: aggregate what’s new dialogs across simultaneously updated plugins

1.11.0 (2026-07-29)

Features

  • plugin: add Knowii community to the what’s new dialog and harden it

1.10.0 (2026-07-29)

Features

  • plugin: surface per-page render failures instead of dropping silently

1.9.1 (2026-07-29)

Bug Fixes

  • plugin: parse version-1 line blocks (24-byte float points)
  • plugin: warn on unknown line-block versions instead of failing silently

1.9.0 (2026-07-29)

Features

  • plugin: add automatic background sync on a configurable interval
  • plugin: prune orphaned sync state after each cloud refresh

Bug Fixes

  • build: keep the release build compatible with older Bun versions
  • deps: bump fast-uri and brace-expansion past vulnerability advisories
  • plugin: drop 1.13-only declarative settings API for stable Obsidian

1.8.0 (2026-07-27)

Features

  • plugin: show a what’s new dialog once after plugin updates

Reverts

  • Revert “feat(plugin): require Obsidian 1.13 and drop the deprecated imperative settings fallback”

1.7.0 (2026-07-17)

Features

  • plugin: add hover tooltip to notebook sync status dot

1.6.0 (2026-07-17)

Features

  • plugin: require Obsidian 1.13 and drop the deprecated imperative settings fallback

Bug Fixes

  • plugin: use createSpan helper and enum-typed reads flagged by catalog review

1.5.0 (2026-07-17)

Features

  • plugin: make settings searchable via declarative settings API (Obsidian 1.13+)

Bug Fixes

  • plugin: address community review warnings (createEl, redundant assertions, unsafe any)

1.4.4 (2026-07-16)

Bug Fixes

  • auth: never fail plugin load on malformed token file

1.4.3 (2026-06-17)

1.4.2 (2026-05-30)

Bug Fixes

  • sync: send rm-filename header on /sync/v3/files requests

1.4.1 (2026-05-15)

Bug Fixes

  • all: fixed bounds calculation before rendering the images

1.4.0 (2026-05-15)

Features

  • all: enable folding folders in the panel

1.3.7 (2026-05-15)

1.3.6 (2026-05-15)

1.3.5 (2026-05-15)

1.3.4 (2026-05-15)

1.3.3 (2026-05-14)

Bug Fixes

  • plugin: rename sync command id to satisfy lint rule

1.3.2 (2026-05-13)

1.3.1 (2026-05-13)

1.3.0 (2026-03-25)

Features

  • all: added refresh button in remarkable panel
  • all: updated

1.2.0 (2026-03-08)

Features

  • all: updated

1.1.0 (2026-03-08)

Features

  • all: optimized images. Added support for WebP. Set JPG by default

1.0.0 (2026-03-08)

Features

  • all: added rmFakeCloud support

0.2.0 (2026-03-07)

Features

  • all: added support for importing rmdoc files

0.1.0 (2026-03-07)

Features

  • all: added fuzzy search
  • all: automatically list the notebooks when the panel opens
  • all: better sync pages
  • all: code cleanup
  • all: handle token expiration and renewal
  • all: improved buttons and search behavior
  • all: improved stroke sizes
  • all: improved stroke width in images (was still too thick)
  • all: initial commit

Bug Fixes

  • all: fixed logging

[0.1.0] - 2026-03-07

Features

  • reMarkable cloud authentication via one-time device code
  • Sidebar panel view listing notebooks with folder hierarchy
  • Per-notebook download (images)
  • .rm v6 binary file parsing for stroke data extraction
  • Page rendering via OffscreenCanvas with 9+ pen types, colors, and opacity
  • Per-page image output
  • Inline progress indicators per notebook in panel
  • Settings for target folder, image format
  • Token storage outside vault for security