0
0
mirror of https://github.com/semver/semver.git synced 2025-08-22 22:08:33 +00:00

Add guidance on non-code file changes

This commit is contained in:
John Trammell 2020-07-23 13:06:30 -05:00 committed by GitHub
parent 2f5ef23b3e
commit 394790ea06
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -334,6 +334,13 @@ Abbreviating "version" as "v" is often seen with version control. Example:
`git tag v1.2.3 -m "Release version 1.2.3"`, in which case "v1.2.3" is a tag
name and the semantic version is "1.2.3".
### What guidance does SemVer offer on file changes that are not code changes?
Each deployed change should have a unique release number. That includes changes
that are not reflected externally in any way, including repository file
permissions, refactoring, performance improvements, and changes to CI/CD pipeline
configurations.
### Is there a suggested regular expression (RegEx) to check a SemVer string?
There are two. One with named groups for those systems that support them