v3.0.1

umami-software/umamiv3.0.1Nov 18, 2025by mikecao

AI Summary

Patch release fixing numerous bugs from v3.0.0 including timezone issues, geo-location tracking problems, and various UI/UX improvements.

Key Highlights

  • Fixed geo-location tracking broken for IPv6 clients
  • Fixed timezone support for local date periods
  • Fixed event data raw query failures
  • Fixed revenue data not showing after upgrade
  • Fixed realtime activity view on mobile

New Features

  • Password managers now detect email field on login form
  • Support for local timezone in date period selection
  • Fixed event data raw query failures
  • Fixed Website Stats API null fields
  • Fixed login page loop issue
  • Fixed geo-location tracking for IPv6
  • Prevented exporting empty datasets
  • Fixed hourly columns in Events view for Today
  • Fixed realtime activity view on mobile
  • Fixed revenue display issues
  • Fixed deprecated timezone Asia/Saigon
  • Fixed long links being cut off
  • Fixed Asia/Calcutta timezone queries

Full Release Notes

This is a patch release that fixes many bugs.

## Fixes
- Password managers unable to detect email field on login form #3735
- Support local timezone for date period #3733
- Event data raw query failure #3732
- Website Stats API Call returns null in some fields #3712
- Loop when login page not accessed directly #3703
- Geo-location tracking (Country) broken in v3.0, showing "Unknown" for majority of visitors #3701 
- UX – Prevent exporting empty datasets #3699
- Events view for "Today" doesn't show all hourly columns #3697
- Realtime activity view basically unusable on mobile #3694
- No Revenue showing after update to 3.0.0 #3692
- Deprecated timezone 'Asia/Saigon' causes PostgreSQL error in Umami (chart shows empty) #3691
- Support local timezone for date period #3733
- Long links are cut off #3680
- Queries fail with Asia/Calcutta timezone → Postgres 22023 / Prisma P2010 (Umami 2.19.0) #3660
- Location statistics broken when tracking IPv6 clients #3616
- Invalid reference to FROM-clause entry for table "session_data" at character 362 #3545

## Thanks
@Maxime-J @Mintimate @prince0xdev @mathis5711