From 394790ea061d9db5681a439421a1ed00c8beb3e5 Mon Sep 17 00:00:00 2001
From: John Trammell <57233065+JohnTrammellTarget@users.noreply.github.com>
Date: Thu, 23 Jul 2020 13:06:30 -0500
Subject: [PATCH] Add guidance on non-code file changes

---
 semver.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/semver.md b/semver.md
index bdde525..778cfe0 100644
--- a/semver.md
+++ b/semver.md
@@ -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