[DEVOPS] - Automatic versioning of the mod

[Gilly7CE]

I want a mechanism for automatically versioning the mod as it can be easily forgotten when publishing a release. Some options:

• Git commit messages
  • Conventional commits is good for "standard" software development but might not work as well for a minecraft mod
  • Custom commit message standard could help, but enforcing it is the tricky bit (Husky is good for sharing git hooks but I personally have no clue how to implement it outside of npm)
• Pull request merge commits
  • The merge (or squash) commit of a PR will indicate the type of incremental change required.
  • Doesn't really work with our
• Branch
  • If merging a PR to main, then increment a "dev" version.
  • If not main, then it is a release version

Opens up the question of whether the branch approach we take to releases is correct, and whether we should follow something like TIS carpet addons with 1 branch for all versions supported. 1 branch would help with versioning massively, and tags would be simpler.