Watchman 1.3.0 stores a history of downloaded list refreshes in MySQL or PostgreSQL so callers can see when a list actually changed and which sourceIDs were added, removed, or updated.
Lists
- After each successful download refresh, Watchman writes a per-list delta keyed by the list file hash from
GET /v2/listinfo. Search still uses the in-memory corpus; history is stored after the index swap. New endpoints:GET /v2/lists,/v2/lists/{listName}/refs,/entities,/entities/{sourceID}, and/diff. Uses the existingDatabaseblock (no new YAML keys). Without a database the history endpoints return HTTP 501. by @adamdecaf in #1018
Search result impact
- Search scores are unchanged.
/v2/searchstill reads the live in-memory corpus./v2/listsis snapshot history at a list hash, including rows that later refresh removed.
Docs
- docs: list the US Restricted Parties affiliates feed and point at the covered file. by @adamdecaf in #1025 and #1026
Fixes
- deps: renovate updates (openrouter go-sdk, golang.org/x/net, ruby/setup-ruby, actions/setup-go)
Full Changelog: v1.2.4...v1.3.0