Versioning style/change log tools
Wasnt too sure where to put this as it is more of a general enquiry, but it might be handy for anyone looking into a similar thing in the future.
Do any of you guys declare the version of any of your releases, and if so are you doing this manually, and what sort of style do you go with?
For the past couple years I've been using semantic versioning with a related change log manually, but I didnt know if there was any alternatives or suggestions that you guys would recommend.
Sometimes I feel like I forget to add a change to the log that I was meant to list at times 😅🤣
2 Replies
last programming job I worked, we did versioning kinda sorta based on semver, but it was pretty loose. Any time we brought code to production, we added 0.0.1. If we added a big enough feature, we added 0.1 and reset the last digit. We kinda saved major versions for either rewrites or entire new sections of the app
it was all manual though, I was usually the one creating the release tags in gitlab, and I just typed it in
One option is https://www.conventionalcommits.org/en/v1.0.0/ which uses your commit messages to build a change log, and update versions.
Conventional Commits
Conventional Commits
A specification for adding human and machine readable meaning to commit messages