# Yente 4.2.2 patch release

**URL:** <https://discuss.opensanctions.org/t/yente-4-2-2-patch-release/73>\
**Category:** Announcements\
**Tags:** release, yente, announcements\
**Created:** [March 14, 2025, 12:23pm UTC](https://discuss.opensanctions.org/t/yente-4-2-2-patch-release/73 "2025-03-14T12:23:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pudo](https://dub1.discourse-cdn.com/flex014/user_avatar/discuss.opensanctions.org/pudo/32/1_2.png) [@pudo](https://discuss.opensanctions.org/u/pudo)\
**Post date:** [March 14, 2025, 12:23pm UTC](https://discuss.opensanctions.org/t/yente-4-2-2-patch-release/73/1 "2025-03-14T12:23:06Z")

</div>

Who said you shouldn’t release software on a Friday? They clearly didn’t have the right spirit. Anyway, there’s a maintenance release for `yente`, which brings in some routine dependency upgrades and tiny fixes, but does not alter core functionality.

## What’s Changed

- Improved country/territory support (e.g. jurisdictions like `ae-du` now map to their main country)
- Smaller Docker image by using multi-stage builds (thanks @legal90 !)
- Expose an ASGI app that can be run by `uvicorn` directly (`uvicorn yente.asgi:app`)
- Removed legacy (and confusing) `fuzzy` flag from `/match` API
- Adopt pyproject.toml for Python library management

See: [Release v4.2.2 · opensanctions/yente · GitHub](https://github.com/opensanctions/yente/releases/tag/v4.2.2)  
How to upgrade: [How can I upgrade yente to the latest version? - OpenSanctions](https://www.opensanctions.org/faq/160/yente-upgrade/)

---

<div class="post-metadata">

**Author:** ![pudo](https://dub1.discourse-cdn.com/flex014/user_avatar/discuss.opensanctions.org/pudo/32/1_2.png) [@pudo](https://discuss.opensanctions.org/u/pudo)\
**Post date:** [March 18, 2025, 12:10pm UTC](https://discuss.opensanctions.org/t/yente-4-2-2-patch-release/73/2 "2025-03-18T12:10:20Z")

</div>

yente 4.2.2 made some changes to how the application is launched within the Docker container, which caused it not to boot up properly in certain deployment contexts.

There is now a new release, 4.2.3, which reverts a small change and should fix this issue. Please run `docker compose pull` or update the Docker image tag ([https://www.opensanctions.org/faq/160/yente-upgrade/](https://www.opensanctions.org/faq/160/yente-upgrade/)) if you’re having issues with running yente 4.2.2.

---

<div class="post-metadata">

**Author:** ![jbothma](https://dub1.discourse-cdn.com/flex014/user_avatar/discuss.opensanctions.org/jbothma/32/14_2.png) [@jbothma](https://discuss.opensanctions.org/u/jbothma)\
**Post date:** [March 20, 2025, 4:38pm UTC](https://discuss.opensanctions.org/t/yente-4-2-2-patch-release/73/3 "2025-03-20T16:38:20Z")

</div>

yente 4.2.2 switched from an ubuntu base image to a slim debian-based image.

This didn’t include curl, which is sometimes used for Docker Compose healthchecks.

We have released yente 4.2.4 making curl available at runtime again.