Yente 5.3 - spring cleaning in /match and stability improvements

Announcements
,
1

Note: Triggers full index rebuild

This release contains the usual round of upgrades to our whole stack, as well as the following changes and improvements:

  • we’ve removed the matcher and features fields from /match API responses. Information equivalent to the matcher field is available via the /algorithms route. To replace features, the explanations field has been added a while ago that is a strict superset of features. In addition to the partial scores produced by each component of the matching system, it includes textual descriptions of the matching decisions from each of these subsystems.

  • a bunch of improvements around failures in clone_index, which is used when yente updates its index to a new version using delta files. A failed clone would previously leave the system in a stuck state which would have to be fixed manually. Thanks @dimoschi for finding this bug, investigating and collaborating on the resolution!

Just as a heads-up: Elasticsearch 8 is nearing its end of life in January 2027. We will release the last version of yente that is compatible with Elasticsearch 8 servers in May 2026. We’ve added a section on that transition in the documentation. TL;DR: upgrade your Elastic server to 8.19.13 first, restart Elastic, then upgrade to 9.x, restart Elastic, and all should go smoothly - please let us know if not! Consequently, we’ve set the version of the Elastic server in the docker-compose.yml to 8.19.13 for now.

As usual, this release contains updates to our whole stack, including an upgrade of the cryptography package to 46.0.6.

See the full changelog at Release v5.3 · opensanctions/yente · GitHub.

1 Like