-
Notifications
You must be signed in to change notification settings - Fork 70
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
Semantic version implementation #21
Comments
Hello Thank you for brining this issue. I implemented a simplified way of versioning for Databunker. During the code build and container build process, the version is taken from this file: https://github.com/securitybunker/databunker/blob/master/version.txt Let me know if this is ok, Otherwise let's have a chat to understand your requirements. Yuli |
I made another changes in build.sh script to generate version as you suggested. Check now:
I publish containers with 0.8.2 and latest tags. Best regards |
Hi Yuli. Thanks for the great project.
To avoid bugs happen in our application that due to new code or new release of databunker. Could you please implement semantic version for each release instead of always use latest? To make it simpler, I think we can use the pseudo-version number style, i.e
Ref: https://go.dev/ref/mod#pseudo-versions
it has three parts
To make it simpler we can alway use the same base version prefix for each version.
How do you think? Thank you.
The text was updated successfully, but these errors were encountered: