fix(versioning): match both branch names so cross-branch versioning is correct

Author: TomGrobbe

GitVersion.yml

@@ -17,8 +17,15 @@ assembly-file-versioning-scheme: MajorMinorPatch
 mode: Mainline
 
 branches:
-  legacy:
-    regex: '^legacy$'
+  # Both release branch names match on purpose, even though this file is only ever read
+  # from legacy. The GitHub Actions runner tells GitVersion which branch it is on through
+  # GITHUB_REF, and GitVersion trusts that over the branch actually checked out. The
+  # combined pipeline checks out the OTHER branch to version it, so a run triggered from
+  # fivem-enhanced would otherwise find no matching entry here, fall back to the default
+  # config and label the build 3.2.26-fivem-enhanced.0. Matching both names makes the
+  # answer depend on the repository being read rather than on which branch triggered.
+  mainline:
+    regex: '^(legacy|fivem-enhanced)$'
     increment: Patch
     is-mainline: true
     # An empty tag means no pre-release label, so builds are a plain 3.2.25. GitVersion