Currently, our GitHub Action is set up to push Docker containers with the latest tag. This means that we're overwriting the existing container in the Docker registry every time we push, and we're not keeping older versions of the container around.
Proposed Solution
To make it easier for users to rollback to previous versions of the container, we propose modifying the GitHub Action to push containers with a version tag instead of the latest tag. This will allow us to keep all versions of the Docker container in the registry.
Benefits
This change will provide the following benefits:
Users will be able to rollback to previous versions of the Docker container if needed.
We will have a history of all versions of the Docker container in the registry, which could be useful for debugging and development purposes.
linear[bot]
commented
2 months ago
Description
Currently, our GitHub Action is set up to push Docker containers with the
latesttag. This means that we're overwriting the existing container in the Docker registry every time we push, and we're not keeping older versions of the container around.Proposed Solution
To make it easier for users to rollback to previous versions of the container, we propose modifying the GitHub Action to push containers with a version tag instead of the
latesttag. This will allow us to keep all versions of the Docker container in the registry.Benefits
This change will provide the following benefits: