PAGES

Claim history

Since v1.103.0, the config file now takes precedence over the database on any key it declares — the previous behavior (database rows deep-merged over the file, so the database value won) is reversed. If you have keys in both the file and the database, the database values are silently ignored; to restore the old behavior, remove those keys from the file so the database owns them again. Our best guess
Claim history
  1. Revision 1 · · Our best guess

    Since v1.103.0, the config file now takes precedence over the database on any key it declares — the previous behavior (database rows deep-merged over the file, so the database value won) is reversed. If you have keys in both the file and the database, the database values are silently ignored; to restore the old behavior, remove those keys from the file so the database owns them again.

    machine summarizer

Saved in this browser. Sign in to sync your tools.