There are three types of semantic versioning:
Major version: when you make incompatible API changes Minor version: when you add functionality in a backwards compatible manner Patch version: when you make backwards compatible bug fixes and minor changes
Following the semantic versioning spec helps other developers who depend on your code understand the extent of changes in a given version, and adjust their own code if necessary. You can read more detailed information about semantic versioning on SemVer.org.
Semantic versioning at the VA
At the VA, semantic versioning is a hard requirement for teams that don’t follow another naming convention system specific to their projects.
The semantic version name should follow the format vX.X.X (example: v2.7.1) and should be used for both the tag version
and the release title
. This enables a consistent convention across the VA organization and additional ease in traceability for releases when used.