Upgrading with building a docker image

Hi, before reporting a bug thought i would ask if it actually is a bug :smiley:

We have been running Mattermost community edition for a couple of years and are happy with it, we have our own minor changes related to getting our own certificate into the docker image and thus we always have updated as follows:
cd /opt/mattermost-docker/
git stash
git pull (from master of mattermost/mattermost-docker/ in github)
git stash pop
docker-compose down
docker-compose build
docker-compose up -d

A little bit of waiting and so far has worked like a charm.

Now in February when trying to update from version 5.31.0 to 5.32.1 was complete i was surprised that version number was still 5.31.0 after our upgrade procedure, a bit of digging later it came out that the reason is that the master branch of mattermost-docker/Dockerfile at master · mattermost/mattermost-docker · GitHub still has 5.31.0 listed as the version.
Was waiting for some days thought that somebody just forgot to change that but now have started doubting as surely someone else using docker should have noticed that as well.

So finally the question - is it an accident that the mattermost-docker/Dockerfile at master · mattermost/mattermost-docker · GitHub has still previous mayor version set or is it intentional? :slight_smile:

There is a PR open to add a known issue that upgrading to release-5.32 fails because PostgreSQL 10+ is required
Known issue about 5.32 version by nvjacobo · Pull Request #523 · mattermost/mattermost-docker · GitHub. More details at PostgreSQL 9.4 deprecated · Issue #489 · mattermost/mattermost-docker · GitHub.