[Feature Request] docker image tags for 2.x and 3.x

[cweiske]

Description

It would be nice if there were tags for the latest 2.x docker image, and the latest 3.x image.

When updating my paperless 2 docker installation today, I knew already that a 3.x was out and that I had to be careful. The v3 migration guide says

Upgrading to Paperless-ngx v3 can only be performed from version 2.20.15. If you are running an older version, please upgrade to v2.20.15 before proceeding with the v3 upgrade.

Had I just done the usual update steps (docker compose down, ... pull, ... up -d), then I would have gotten a 3.x version but with a database state of 2.12.0.

Pinning the compose file to a major version would help against that problem, but this is not possible right now - the docker images offer minor and patch level tags, but not major version tags.

Please provide tags for major versions:

• ghcr.io/paperless-ngx/paperless-ngx:2
• ghcr.io/paperless-ngx/paperless-ngx:3

and use them in the provided docker-compose.yml files.

Other

No response

[stumpylog]

There will never be another 2.x release. The choice to provide only feature release tags is deliberate and not likely to be revisited.

[cweiske]

Then the problem will reappear with the v4 release.

[FEmser]

Exactly this. I constantly have to check and update the minor version in the docker compose. Now again from :3.3 to :3.4.
I dont want to use :latest since I would be stressed about missing a possible v4 release and upgrade by accident.
Most other projects provide major release tags but paperless is not yet.
I would be glad if major tags were used.

[JanKleine]

An easy counter argument would be that there will also never be another 2.20.x release so why does 2.20 have a tag? I personally have moved to renovate for updates, which can be configured nicely to highlight/separate major version updates, but for simple docker compose setups a major only tag would indeed be convenient (analogous to postgres in the sample compose files in this repo).

Since fixes are currently never back ported to previous versions, it could be argued that a major version tag is more useful than a feature tag as it stays relevant/current for longer.