5 posts tagged with "feature"

Published on August 14, 2026

Uni-Verein 1.5.0 brings one of the biggest new features since launch: receipt management. Receipts and invoices can now be submitted directly in Uni-Verein, automatically read via on-device OCR, and visualized by month, category, and year in a brand-new receipt analytics dashboard.

Highlights​

• 🧾 Receipt management: Members submit receipts or invoices as a photo or PDF, while admins and finance managers stay on top of them with filters, payment status, and ZIP export
• 🤖 On-device OCR scan: Amount and receipt date are read straight from the photo in the browser, no server request required
• 📊 Receipt analytics: Expenses by month and category as bar and pie charts, plus a year-over-year comparison
• 💾 Full backup with receipts: Backups can now optionally include all uploaded receipt files as a ZIP

New Features​

• 📎 Receipt management: A new "Receipts" section where regular users see their own submissions, while admins and finance managers see all submitted receipts including who submitted them. The list can be filtered by period, category, and status (open/paid)
• 🤖 OCR scan on submission: When uploading a photo or PDF, the receipt is scanned directly in the browser using on-device OCR and automatically fills in the amount and receipt date, without overwriting fields that are already filled in. Merchant, category, payment method, and description can be added manually as well, payment method can only be set by admins and finance managers
• 📸 Direct camera button: When the app is installed, submitting a receipt offers a dedicated camera button in addition to the regular file upload
• ✅ Mark as paid: Admins and finance managers confirm receipts as paid, an action that can't be undone afterwards. Regular users can only edit or delete their own, still-open receipt within 15 minutes of submitting it
• 🗑️ Delete & restore: Deleted receipts are soft-deleted first (trash-can principle). Admins can show deleted receipts in the list, restore them, or permanently delete them along with all attached files
• 📤 Export as ZIP: Admins and finance managers can export the currently filtered receipt list as a ZIP containing a CSV overview and all attached files
• 📊 Receipt analytics: A new analytics area for admins and finance managers with a bar chart of expenses per month (stacked by category), a pie chart per category with the year's total in the middle, and an overview comparing total expenses across years
• 🏷️ Manage receipt categories: A new setting for creating custom categories such as office supplies, travel expenses, or catering, a category can only be deleted once no receipt is assigned to it anymore

Improvements​

• 💾 Backup with receipts: In addition to the regular database backup, a full backup including all uploaded receipt files is now available as a ZIP download. When restoring, Uni-Verein automatically detects whether a plain SQL file or a full ZIP backup was selected, both can be restored via "Select backup file"

Why These Updates Matter​

Receipt and expense management has been one of the most-requested features from club treasurers: instead of collecting receipts and entering them into a spreadsheet by hand, members now submit them directly in Uni-Verein, with the OCR scan taking care of most of the typing. For the board and finance managers, the new receipt analytics dashboard provides instant visibility into spending, no separate spreadsheet required.

What's Next?​

Receipt management is a first step toward more comprehensive financial features, real-world feedback is, as always, very welcome via GitHub Issues. Check back here again soon!

Published on July 28, 2026

Uni-Verein 1.4.0 is here – with a long-requested dark mode and a bigger change under the hood: the database engine switches from MariaDB to PostgreSQL. Existing installations are migrated automatically and safely by the updater.

Highlights​

• 🌓 Dark mode: the app now follows your OS/browser color scheme by default, with a manual toggle next to the language switcher
• 🐘 PostgreSQL instead of MariaDB: the database engine has been switched to PostgreSQL. Existing installations are migrated automatically and safely by the updater (see Important Upgrade Notes below)

⚠️ Important Upgrade Notes (Breaking Change)​

This release changes the database engine from MariaDB to PostgreSQL. Always update using the official updater never set VERSION in .env by hand or swap in a newer docker-compose-prod-image.yml yourself, as that skips the required database migration and will break your installation.

curl -O https://raw.githubusercontent.com/uni-verein/uni-verein/main/docker-compose-update.yml
docker compose -f docker-compose-update.yml run --rm update

• Before continuing, create a manual backup (database backup and member export, both under Settings → Backup) – the updater asks you to confirm this before it proceeds
• Installations still on MariaDB are updated to v1.3.1 first, if they aren't already there. From v1.3.1, the next update run migrates your database to PostgreSQL and switches the whole stack over. This adds downtime proportional to your database size
• Migration safety net: the cutover runs against an isolated, temporary PostgreSQL instance while your live MariaDB container keeps serving, so nothing is touched until the copy is verified. On success, the old MariaDB container is stopped and its data volume is kept (not deleted) reclaim the space later with docker volume rm <project>_db_data once you've confirmed everything works. On failure, the migration is cleaned up automatically and your MariaDB installation is left completely untouched
• Coming from an older version? The updater only advances one step per run (< v1.3.1 → v1.3.1 → v1.4.0 → latest). If you're updating from before v1.3.1, run the command above repeatedly until it reports "Already up to date"

New Features​

• 🌓 Dark mode: follows prefers-color-scheme by default, or set it manually via a toggle next to the language switcher. The choice is remembered across reloads. Every previously light-only surface (main background, table headers, Backup/Email/SendProgress panels, top bar, login page) is now theme-aware
• 🛠️ UniVerein.DbMigrator: a new tool that performs the MariaDB → PostgreSQL migration described above, copies every table (including soft-deleted rows) in foreign-key-safe order and verifies row counts

Improvements​

• 🐘 Replaced MariaDB with PostgreSQL (postgres:17-alpine) across the whole stack: Docker images, the backend's database provider, and the backup/restore tooling
• 🔄 The updater (docker-compose-update.yml) now understands the MariaDB → PostgreSQL cutover described above and handles it automatically

Bug Fixes​

• 🐛 The demo-mode login dialog could appear even when the app wasn't configured as a demo instance, due to how the demo flag was evaluated

Why These Updates Matter​

Dark mode has been one of the most-requested quality-of-life features, a noticeable difference during evening board meetings, for one. The switch to PostgreSQL, on the other hand, is a strategic decision: it provides a more robust foundation for future features and better data integrity. Since a database engine change is inherently delicate for existing installations, particular care was taken to make the migration safe, automated, and reversible on failure.

What's Next?​

Please plan a short maintenance window for the update, and reach out via GitHub Issues if you run into any problems during the migration. Thanks to everyone who provided feedback for this release. Check back here again soon!

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.

Published on July 22, 2026

Uni-Verein 1.2.0 closes one of the biggest gaps from the project's early days: the software was previously optimized for desktop and tablet only starting now, Uni-Verein also works on smartphones and can even be installed like an app.

New Features​

• 📲 Progressive Web App (PWA): Uni-Verein can now be installed to the home screen
• 📱 Mobile-optimized layout: On smartphones, a hamburger menu with bottom navigation replaces the desktop sidebar, tables collapse into cards or a single-column view, dialogs open full-screen, and filter bars stack vertically
• 📡 Offline indicator on the login screen: Shows "You're offline" whenever there's no connection or the server can't be reached, clearing automatically once reachability returns

Improvements​

• 🧩 Larger frontend refactorings: mobile-specific views (audit log, member list) and the sidebar navigation were extracted into dedicated, reusable components
• 🗂️ The create/edit dialogs (contribution plans, users, member categories, links, import errors, confirm, icon picker, member form) were moved into standalone components under src/components/dialogs
• 📄 A shared ResponsiveTablePagination component is now used by every paginated table (Members, Mail recipients, SEPA, Contributions, Audit)
• ✨ Consistent Prettier formatting applied across the frontend codebase
• ⚙️ The "Update Third-Party Notices" workflow now runs on feature branches instead of main
• 🐳 docker-compose-ini.yml now fetches the current version from the latest GitHub release automatically instead of requiring it to be maintained manually in .env

Bug Fixes​

• 🐛 The language switch button sometimes required two clicks before the language actually changed on first use
• 🐛 The init script (docker-compose-ini.yml) left duplicate VERSION lines in .env because sed -i failed silently against the single-file bind mount

Why These Updates Matter​

Mobile support has been one of the most requested features since the very first release, and it now makes Uni-Verein practical for board work on the go whether checking members in at an event or glancing at the member list between lectures. Thanks to PWA support, the web app also feels almost like a native app, including offline access to already-loaded data.

What's Next?​

This closes an important milestone from the original roadmap. Next up are further performance and infrastructure improvements, be sure to check back here again soon.

Published on July 16, 2026

Uni-Verein 1.1.0 brings the first major feature update since the initial release. This time the focus is on automatic update notifications, along with a few important bug fixes for everyday member management.

New Features​

• 🔔 Automatic update check: Uni-Verein now automatically compares the installed version against the latest GitHub release
• 📧 Admin email notifications: Administrators are automatically notified by email as soon as a new version becomes available
• 🔔 Notification bell in the frontend: A new bell icon in the frontend shows at a glance whether an update is available

Improvements​

• 🗂️ The backend Data folder was renamed to Models for a cleaner project structure
• ⚙️ Adjustments to the CI configuration

Bug Fixes​

• 🐛 Fixed an issue where new members could sometimes be assigned duplicate member numbers

Why These Updates Matter​

The automatic update check ensures organizations always know when a new version of Uni-Verein is available, no more manually checking GitHub. Combined with the fix for member number assignment, everyday work with Uni-Verein becomes even more reliable.

What's Next?​

Thank you to everyone who contributed feedback and bug reports for this release! Work on new features like mobile view and an event calendar continues, so be sure to check back here again soon.