Regarding the VERSION field of the generated Tags class

[a810587921]

How can I make the VERSION field a custom value, such as 1.0, 1.1, instead of the current git version?

[Roadhog360]

Use case:
Currently, I am working on Et Futurum Requiem. The current next in-progress version is 2.6.1. However, because the last tag released was 2.6.0, the jars are labeled as 2.6.0 builds. This is wrong, as these are development jars for 2.6.1, not 2.6.0; 2.6.0 was already released. I'd rather just have them be labeled as 2.6.1 with the proper commit hash, signifying they are 2.6.1 snapshots, for me I only want my releases to follow the latest tag name. So if I released 2.6.1 beta 1 under the tag 2.6.1-beta-1 tag, it'd still use that tag for the release, and I'd like the CI to continue to produce jars that are just called 2.6.1 with a commit hash, since 2.6.1 has not hit a full release and thus these builds are still snapshots leading up to 2.6.1.

As far as I can tell, there's no way to achieve this effect under the current revisions of the script.

[Roadhog360]

Hello @a810587921 Roadhog360/Et-Futurum-Requiem#539

This user has created a version override that provides the desired behavior for me, with an option to remove commit hash for the build too. It allows you to specify a custom version in the file rather than the GitHub version.