Skip to main content

Uni-Verein 1.3.0 – Name Search for Newsletter Recipients and a More Stable Infrastructure 🔍

· 2 min read
René Herrmann
René Herrmann
Senior developer

Published on July 25, 2026

Uni-Verein 1.3.0 brings a handy new search feature for sending newsletters, along with a number of under-the-hood improvements that make deployments and CI runs more reliable.

New Features​

  • 🔍 Name search in the Broadcast email "Recipient" tab: Recipients can now be filtered by first or last name (fuzzy, Jaro-Winkler similarity), in addition to the existing member category filter
  • ❤️ /health endpoint: A new unauthenticated GET /health endpoint plus Docker HEALTHCHECKs for backend and frontend

Improvements​

  • 🩺 backend, frontend, and proxy now have proper health checks (previously only the database did), and each service waits for its dependencies to be actually ready (service_healthy) instead of just started, across all docker-compose*.yml files
  • 🚦 CI now fails immediately with container logs attached when the stack doesn't become healthy in time, instead of silently continuing on to the Playwright tests and failing there with no diagnostics
  • ⏱️ Increased the database health check's retry budget to tolerate occasional slow first-time initialization on CI runners
  • 📝 .env.example now lists BACKUP_PATH, matching every value docker-compose-ini.yml generates
  • 🔒 CI now enforces that PRs into main may only come from development (new enforce-source-branch job)

Bug Fixes​

  • 🐛 The newsletter recipient category dropdown showed the raw translation key instead of the category name for custom (non-default) member categories
  • 🐛 The proxy container could stay unhealthy indefinitely because its health check resolved localhost to IPv6 while nginx.conf only listens on IPv4
  • 🐛 The backend Docker image build occasionally failed due to transient package-mirror errors during apt-get install

Security​

  • 🔐 Pinned sharp to ^0.35.3 via npm overrides to pull in a fixed version instead of the vulnerable transitive one

Why These Updates Matter​

The name search saves a lot of time for larger organizations that need to quickly find individual newsletter recipients. Just as important are the health check improvements: they make deployments start up more reliably and surface CI problems immediately with meaningful logs, instead of only showing up late and without context.

What's Next?​

Work on performance and infrastructure continues, the next release already focuses on noticeably faster load times.