Changelog for Altworx 26.6.0

Database upgraded from PostgreSQL 15 to PostgreSQL 18. Existing deployments must run the pg_upgrade migration — either via deployment hooks (pre-install.d/01-pg18-upgrade.sh and post-install.d/01-pg18-cleanup.sh, available in the empty deployment) or manually using the migration image (altworx/asset_map_database:v5.0.0-migration). See the asset_map_database Readme for details.
Deployments using a custom postgresql.conf must migrate those settings into a tuning config mounted at /etc/postgresql/conf.d/tuning.conf. The upgrade intentionally does not copy postgresql.conf from PG 15 because several parameters were removed or renamed in PG 18. Regenerate settings for PG 18 (e.g. using PGTune) and mount the file as a Docker volume. See the asset_map_database Readme for the volume mount example.

Unify origin checks and fix a bug where ALTWORX_HOSTNAME and [general] ui_url wasn’t used in some checks (PR)
Add futures to incident history (PR, #7531)
Add access tags to incident history (PR, #7530)
Add Firebase subscriptions API (PR, #7685)
Use simplified Google OAuth login flow (PR, #7678)
Add user_actions to incident history (PR, #7532)
Update docker-compose db service for PostgreSQL 18 (PR, #7297)