Container image tag `latest` does not point to newest release

[UiP9AV6Y]

Describe the bug The README.md lists the Docker Hub as the primary source for the container images of this project. The newest release (as of writing this) is 4.2.2 and has a corresponding container image in the Docker Container Registry. The image tagged latest however was pushed to the Docker Container Registry 2 years ago. The Github Workflow responsible for deploying images (CI/main.yml) was manually run 2 years ago. This applies to both the ui and api image

To Reproduce

• Observe the available image tags 1 on the Docker Hub
• Observe the Github Workflow 3 responsible for deploying the images

Expected behavior

By convention container images tagged latest are usually vanity tags pointing to the most recent of releases (usually a stable release; unstable releases are generally tagged as nightly)

Additional context

• It appears the CI workflow for the image release was triggered manually
• It appears container images are deployed to the Docker Container Registry manually rather than via the CI workflow

[Jaydee94]

Hey, @UiP9AV6Y I will have a look at this. Thanks for your bug report.