Skip to content

2.22.0

Choose a tag to compare

@github-actions github-actions released this 12 Aug 02:49
· 39 commits to main since this release

Update every device before you sync

This one is different from 2.21.0, so please read this part first. Your settings and your store move to a new format. A device still on 2.21.0 will meet the new format, decline politely and tell you to update — nothing is damaged. A device on 2.20.0 or earlier will reset its setup to defaults. So update everywhere before letting any device capture or push.

Nothing else is asked of you. Your settings migrate the first time this version opens them, and your store is read as it is until a capture or a pull rewrites it.

Why

The same idea had three different names depending on where you were standing. scope: meant the settings area in one search box, the item category in the other, and — in the file that stores your choices — which devices share a value. Classification was buried inside identifiers, so the plugin was forever reading a category back out of a name. And two settings each rolled two unrelated choices into a single list.

Changed

  • scope: is now section: in both search boxes. The old word had to go, because it named three different things. There is no alias: scope:community finds nothing now, and section:community is what you want. The settings box keeps its own extra values — general, advanced, remotes.
  • Where an item runs and where it is forced on or off are two separate choices, instead of one list mixing them. One consequence to know about: choosing Runs on → Computers only (or Phones only) now also decides whether that item takes part in Capture and Apply. Before, that choice was read by the menu and nothing else.
  • Sharing a value says what it means: shared everywhere, kept per device class, or never leaving this device. A whole-file rule can no longer be set to This device — it never worked, and now it cannot be asked for.
  • Search still matches exactly what it matched before. Only the word changed.

Two smaller differences worth knowing

  • After the migration, a community plugin whose card you had switched off, and which is not installed on this device, loses its card until you install it here. Its settings and its rules are untouched; only the card is gone.
  • On a store still in the old format, an item's display name can look stale until the next capture or pull. The startup name-repair no longer rewrites a store it did not write, because doing so produced a file that older devices could neither refuse nor read.

Node suite at 1515 tests.