Releases · umami-software/umami

Important

This release includes a new database migration. In this update we are making some changes to Events. Now instead of event_type and event_value columns, there is going to be a single renamed column, event_name. Having the two separate columns caused a lot of confusion regarding what to store in each field. There is now a new table called event_data which is used to store event related data. In the future you will be able to run reports against your events and event data.

Now to track events, you simply choose an event name, like button-click and optionally send some JSON data along with it.

umami.trackEvent('button-click', { userId: 123, buttonName: 'Newsletter signup' });

When you start the app for the first time, the database changes will be automatically applied. Your data however will not be automatically migrated because we can't determine what event_name you will want to use. Your old event table has been renamed to _event_old, which you can use to manually move data to the new table. If you've never used events, feel free to delete the _event_old table.

Features

New model for Events ☝️
New languages: Thai and Bengali! 🐯 🥳
Edit dashboard feature. You can now sort websites on the dashboard

UTM parameters section is now Query parameters. This now captures all the URL query parameters, not just UTM
Refactored handling of environment variables. Before, some environment variables had to be defined at built-time versus run-time, which caused a lot of issues for Docker users. With this change we can now access all environment variables at runtime. No need to rebuild the application or Docker image.

Fixes

Updated Docker build to work with COLLECT_API_ENDPOINT
Removed DISABLE_LOGIN check from middleware due to Vercel issues.
Fixed issue with Heroku deploy

Updates

Upgraded Next.js to 12.2.4
Upgraded Prisma to 4.1.1
Language translation updates.

A huge thanks to all the contributors on this release! @cywio @briancao @wangyang0210 @biqette @umarhadi @H0rn0chse

Important

This release will use Prisma migrations for the first time. This will help up make schema changes quickly and easily in the future in order to support new upcoming features. A new script called check-db has been added and will run before starting the app. It verifies that your database connection is defined and working and that your schema is up to date. The script will inform you what commands you need to run to get your database up to date. You need to run the given command manually. The message will looks something like this:

✗ Database is out of date.

You need to update your database by running:

yarn prisma migrate resolve --applied "20210320112717_init"

Also as a result of this change, the installation process will be much easier for new installations. There is no longer a manual database step to set up the tables. It will all be handled through Prisma. Additionally, defining the HASH_SALT environment variable is no longer required, but optional if you still want to use it.

Features

New language: Galacian! 💯
Added IGNORE_HOSTNAME environment variable. This will do a DNS lookup on a hostname and the resulting IP address will be ignored. This can be a comma delimited list of hostnames.
Added DISABLE_UPDATES environment variable which disables the new version check.

Updates

Start using Prisma database migrations.
Removed HASH_SALT requirement.
Language translation updates
Updated Prisma to v3.15.2

Fixes

Fixed display of encoded characters
Moved DISABLE_LOGIN check from middleware to build step since it has been causing issues on Vercel.
Removed password field from accounts query

A huge thanks to all the contributors on this release! @anbraten @userdehghani @bilguun0203 @valtlfelipe @saosangmo @Maxime-J