Harri Häivälä

I have been doing this for years. I have running instance and I change the version number and run: (`dc` is alias for `docker-compose`) `dc build --pull; dc up -d`...

Anyone else find this alarming?

Are we getting scripted version of the update from the maintainers?

DB upgrade is now required..

> The 5.32 is released now. Is pg 9.4 still compatible for 5.32? No.

> Thanks for letting us know! The issue was escalated earlier, and our build engineer will be looking at this. Any news on this?

I had same problem and I don't know if it's related but I had to chown the `volumes/app/mattermost/data` folder for the right user.

I have this too with mariadb 10.7.4 and 10.7.6. `ALTER TABLE media__media CHANGE provider_metadata provider_metadata LONGTEXT DEFAULT NULL COMMENT '(DC2Type:json)';`

I just upgraded: `"doctrine/doctrine-migrations-bundle": "^2",` to `"doctrine/doctrine-migrations-bundle": "^3",` and migration is not generated anymore.

These are the packages that upgraded with it ``` - Upgrading doctrine/dbal (2.13.9 => 3.4.5) - Upgrading doctrine/doctrine-migrations-bundle (2.2.3 => 3.2.2) - Upgrading doctrine/migrations (2.3.5 => 3.5.2) ```