Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement better way to release new version #42

Open
crozzy opened this issue Feb 14, 2023 · 0 comments
Open

Implement better way to release new version #42

crozzy opened this issue Feb 14, 2023 · 0 comments

Comments

@crozzy
Copy link
Collaborator

crozzy commented Feb 14, 2023

Currently the CI to cut a new Release takes a tag and checks that the Dockerfile has been updated with the new tag. If it hasn't, the release process fails. This is a weird chicken and egg situation where you need to prepare the code for a tag before it exists, but doing it after doesn't work either.

This probably merits a prepare-release workflow that creates the PR iterating the image version in the Dockerfile that needs merging before cutting a tag. It doesn't totally solve the situation but at least gives the operator a better defined procedure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant