When writing settings files, if the validated content would drop entries that the current build doesn't recognize but that should still be preserved, the writer now falls back to the raw on-disk JSON so those unrecognized entries survive the write instead of being silently dropped.
Settings writer falls back to raw file when validation errors should be preserved
Settings entries this build does not recognize now survive a write, via a fallback to the raw file on disk.
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SettingsArea: what it touches
Bug FixesKind: in v2.1.257,
Bug FixesSection of the release