This can never be complete, but it should be doable and useful to update tag-release to validate that the release number:
Consists of some number of integers, separated by periods, with no other characters (An exception can be made for tags at the end - ie 2.0.0-beta or 1.9.9a
Is greater than any/the most recent release tag in git
Consider switching this to instead provide a scope - IE tag-release.sh minor, and having the script automatically compute the new version number.
This would however incur future costs to support format changes - IE a beta release would need a --type sort of flag, and adding more than major.minor.patch.build would require some way to pass that into the script.
This can never be complete, but it should be doable and useful to update tag-release to validate that the release number:
2.0.0-betaor1.9.9aConsider switching this to instead provide a scope - IE
tag-release.sh minor, and having the script automatically compute the new version number.This would however incur future costs to support format changes - IE a beta release would need a
--typesort of flag, and adding more thanmajor.minor.patch.buildwould require some way to pass that into the script.