added that it increments the version number

WTGPublishPackageGuide.md

@@ -3,7 +3,7 @@
 This doc explains how the package we use at WTG is updated.
 
 ## Creating Releases with Github Actions
-When a PR is **merged to master**, the GitHub Action 'Create release' should run. It can also be run manually if needed. This action creates a GitHub Release and uploads the package to the release. The package created should contain Blazor.Diagrams.dll, Blazor.Diagrams.Core.dll and SvgPathProperties.dll.
+When a PR is **merged to master**, the GitHub Action 'Create release' should run. It can also be run manually if needed. This action builds the package, increments the version number, creates a GitHub Release, and uploads the package to the release. The package created should contain Blazor.Diagrams.dll, Blazor.Diagrams.Core.dll and SvgPathProperties.dll.
 
 This action also pushes this release to NuGet, see [WTG.Z.Blazor.Diagrams on nuget](https://proget.wtg.zone/feeds/Gallery/WTG.Z.Blazor.Diagrams/versions). We access this internally at WiseTech through ProGet, see [WTG.Z.Blazor.Diagrams on proget](https://proget.wtg.zone/feeds/Gallery/WTG.Z.Blazor.Diagrams/versions). See [this article](https://inedo.com/proget/private-nuget-server) for more info about how and why proget is used as a source for NuGet rather than accessing NuGet directly.