# Yente 5.3 - spring cleaning in /match and stability improvements

**URL:** <https://discuss.opensanctions.org/t/yente-5-3-spring-cleaning-in-match-and-stability-improvements/268>\
**Category:** Announcements\
**Tags:** yente, announcements\
**Created:** [April 1, 2026, 9:57am UTC](https://discuss.opensanctions.org/t/yente-5-3-spring-cleaning-in-match-and-stability-improvements/268 "2026-04-01T09:57:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![leon.handreke](https://dub1.discourse-cdn.com/flex014/user_avatar/discuss.opensanctions.org/leon.handreke/32/38_2.png) [@leon.handreke](https://discuss.opensanctions.org/u/leon.handreke)\
**Post date:** [April 1, 2026, 9:57am UTC](https://discuss.opensanctions.org/t/yente-5-3-spring-cleaning-in-match-and-stability-improvements/268/1 "2026-04-01T09:57:37Z")

</div>

_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](https://github.com/dimoschi) for [finding this bug, investigating and collaborating on the resolution](https://github.com/opensanctions/yente/issues/1033)!

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](https://yente.followthemoney.tech/deploy/upgrading/). 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](https://github.com/opensanctions/yente/releases/tag/v5.3.0).