Merge pull request #1083 from flcdrg/patch-1

Add link to version number normalisation page
chocolatey · Dec 25, 2024 · 584a87f · 584a87f
2 parents d901e91 + f574888
commit 584a87f
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/src/content/docs/en-us/create/create-packages.mdx b/src/content/docs/en-us/create/create-packages.mdx
@@ -363,6 +363,8 @@ Versioning can be both simple and complicated. The best recommendation is to use
 
 If the 4th segment is used, some folks like to drop the segment altogether and use that as only the package fix notation using one of the notations in the next section. There is no recommendations at this time.
 
+See also <Xref title="Version number normalization" value="version-normalization" />.
+
 ### Package Fix Version Notation
 
 Package fix version notation ONLY applies when you are making a fix to the package because the existing version of a package is incorrect in some way. So if the software is `1.1.0`, in a normal scenario the package version should be `1.1.0`. If you find that the `1.1.0` package has an issue and you need to fix the package but keep the same version of the software, that is where package fix version notation comes into play. You would end up with both a `1.1.0` package and a `1.1.0.YYYYMMDD` version of the package.