Will an upgrade from v2.5.1 to v4.0.1 work?

[SysEngDan]

Hi all,

I'm on v2.5.1. Do I need to upgrade to v3.0.0 or can I go straight to v4.0.1? I'm using the Docker images.

[knadh]

You can upgrade directly to the latest version.

Just to be safe, please take a backup of your database and for upgrading, follow the instructions in the release notes.

[SysEngDan]

I'm happy to report that the update worked successfully.

[JamesChevalier]

Do you recall the exact steps you took? I'm in a state (#2112) where the update from PostgreSQL 13->17 isn't working.

• curl -LO https://github.com/knadh/listmonk/raw/master/docker-compose.yml
• mv docker-compose.yml listmonk/docker-compose.yml.new
• cd listmonk
• Edit the POSTGRES_PASSWORD and hostname entries in the docker-compose.yml.new file
• docker compose down app
• mv docker-compose.yml docker-compose.yml.old
• mv docker-compose.yml.new docker-compose.yml
• docker compose pull
• docker-compose run --rm app ./listmonk --upgrade

It fails to connect to the db container because it's in a restart cycle, because the data it has is from v13.
Maybe there's another approach to handling the old/new docker-compose.yml files...