Currently the workflow for this repository does not create any GitHub releases nor changelogs. Also, it is tricky to track changes in container images as they only contain the OpenVPN tag. This poses a problem where changes end up overwriting existing container images.
Ideally we should update the workflow to account for PRs and changes that will happen in the future, and build images with two tags in mind: one for OpenVPN version, and another one for a build ID. This way changes for the same OpenVPN version (e.g. 2.6.6) would results in different container images being build rather than overwriting the tags.
Currently the workflow for this repository does not create any GitHub releases nor changelogs. Also, it is tricky to track changes in container images as they only contain the OpenVPN tag. This poses a problem where changes end up overwriting existing container images.
Ideally we should update the workflow to account for PRs and changes that will happen in the future, and build images with two tags in mind: one for OpenVPN version, and another one for a build ID. This way changes for the same OpenVPN version (e.g. 2.6.6) would results in different container images being build rather than overwriting the tags.