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

Add automatic version arguments to the CI pipeline. #8

Closed
tmeire opened this issue Aug 23, 2024 · 1 comment
Closed

Add automatic version arguments to the CI pipeline. #8

tmeire opened this issue Aug 23, 2024 · 1 comment

Comments

@tmeire
Copy link
Owner

tmeire commented Aug 23, 2024

TODO: Define a versioning strategy and pass in the automated version to the docker build process.

@tmeire
Copy link
Owner Author

tmeire commented Aug 26, 2024

Development should follow a trunk-based development flow with semantic versioning. New versions need to be tagged manually. Preferably, each minor release has its own release branch release-X.Y where (pre-)releases are tagged with a tag like vX.Y.Z(-rc.W). Tags will trigger the build workflow which will push the docker image to ghcr on success.

Fixed in #14

@tmeire tmeire closed this as completed Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant