Maintenance

Operating system dependencies

Dependency	Location	URL
Slim bookworm Python Docker image	https://github.com/nationalarchives/docker/blob/main/docker/tna-python/Dockerfile#L3	https://hub.docker.com/_/python/tags?name=slim-bookworm
libcurl4	https://github.com/nationalarchives/docker/blob/main/docker/tna-python/Dockerfile#L111	https://packages.debian.org/sid/libcurl4
curl	https://github.com/nationalarchives/docker/blob/main/docker/tna-python/Dockerfile#L111	https://github.com/curl/curl/releases
build-essential	https://github.com/nationalarchives/docker/blob/main/docker/tna-python/Dockerfile#L111	https://packages.debian.org/source/sid/build-essential
libmagic-dev	https://github.com/nationalarchives/docker/blob/main/docker/tna-python/Dockerfile#L111	https://packages.debian.org/sid/libmagic-dev

Tools and libraries

A specific version of each tool is declared in code. Upgrading is therefore a concious action.

Dependency	Location	URL
Poetry	https://github.com/nationalarchives/docker/blob/main/docker/tna-python/Dockerfile#L143	https://github.com/python-poetry/poetry/releases
nvm	https://github.com/nationalarchives/docker/blob/main/docker/tna-python/Dockerfile#L144	https://github.com/nvm-sh/nvm/releases
NodeJS	https://github.com/nationalarchives/docker/blob/main/docker/tna-python/Dockerfile#L181	https://github.com/nodejs/node/releases
gunicorn	https://github.com/nationalarchives/docker/blob/main/docker/tna-python/bin/tna-build#L22	https://github.com/benoitc/gunicorn/releases
uvicorn	https://github.com/nationalarchives/docker/blob/main/docker/tna-python/bin/tna-build#L23	https://github.com/encode/uvicorn/releases
uvicorn-worker	https://github.com/nationalarchives/docker/blob/main/docker/tna-python/bin/tna-build#L24	https://github.com/Kludex/uvicorn-worker/releases

Keeping everything up-to-date

Subscribe to new releases for all the tools.

When a new version is released:

1. Change its version in the required place.
2. Update the CHANGELOG.md by adding the updated resource in "Changed", "Removed", "Fixed" or "Security"
3. The build workflow will be run for the image version called preview and the image added to the container repository
4. If ready, release a new version

Release a new version

1. Update the CHANGELOG.md and specify a version that adheres to semver
2. Push all changes to main
3. Create a new release with the version number, ensuring there is a leading v
4. The build workflow will be run and the image added to the container repository