Umami - Package Updates

[girish]

You can use this thread to track updates to the Umami package.

Please open issues in a separate topic instead of replying here.

[girish]

[0.1.0]

• Initial version

[girish]

[0.2.0]

• Add tests

[girish]

[1.0.0]

• Update Umami to 1.31.0
• Full changelog
• The url filter now also filters events
• Language translation updates
• Fixed display issue with unknown countries
• Fixed issue with All time filter not working on shared pages

[girish]

[1.1.0]

• Update Umami to 1.32.1
• Full changelog
• Use fetch instead of navigator.sendBeacon in tracker script
• Language translation updates
• Updated Prisma to v3.14.0

[girish]

1.2.0]

• Update Umami to 1.33
• Full changelog
• New language: Galacian! 100
• Added DISABLE_UPDATES environment variable which disables the new version check.
• Start using Prisma database migrations

[girish]

[1.2.1]

• Update Umami to 1.33.1
• Full changelog

[girish]

[1.3.0]

• Update Umami to 1.34.0
• Full changelog

[girish]

[1.4.0]

• Update Umami to 1.35.0
• Full changelog
• Fixed issue with COLLECT_API_ENDPOINT not working. Note, you need to set this at build time to work. See https://umami.is/docs/environment-variables
• Fixed chart issues in MySQL
• Updated language translations

[girish]

[1.5.0]

• Update Umami to 1.36.0
• Full changelog
• UTM sources are now available in the More details section
• Fixed issue with event queries passing the wrong parameters
• Fix bounces/time display for MySQL
• Language translation updates

[girish]

[1.5.1]

• Update Umami to 1.36.1
• Full changelog
• Fixed issue with sessions being loaded incorrectly
• Language translation updates

[girish]

[1.6.0]

• Update Umami to 1.37.0
• Full changelog
• New model for Events point_up
• New languages: Thai and Bengali! tiger partying_face
• 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

[girish]

[2.0.0]

• IMPORTANT: The database upgrade fails if you have been running umami for a while. There is no easy work around for this, you can manually try the database modifications in this upstream bug after you upgrade and place the app in Repair mode.
• If possible, just start with a fresh installation of Umami. It can be quite a time sink to fix the database schema and you might still hit some issue later in future versions.