Update instances in documentation where version number should always reflect current version

AristurtleDev · AristurtleDev · commit 74b2c66e4cef · 2025-11-19T22:45:29.000-05:00
diff --git a/articles/getting_started/1_setting_up_your_os_for_development_arch.md b/articles/getting_started/1_setting_up_your_os_for_development_arch.md
@@ -6,7 +6,7 @@ description: This section provides a step-by-step guide for setting up your deve
 > [!TIP]
 > Arch Linux is a rolling release distribution. This guide was tested in October 2025 with kernel `version 6.15.9-arch1-1`.
 
-To develop with MonoGame in C#, you will need to install the .NET 9 SDK. As of MonoGame 3.8.4.1 the recommended version is .NET 9.
+To develop with MonoGame in C#, you will need to install the .NET 9 SDK. As of MonoGame {{mgVersion}} the recommended version is .NET 9.
 
 > [!TIP]
 > You can still continue to use .NET 8 if you wish, you will just need to downgrade your client project .NET version in the `csproj` setup for your project (if using the default templates)
diff --git a/articles/getting_started/1_setting_up_your_os_for_development_macos.md b/articles/getting_started/1_setting_up_your_os_for_development_macos.md
@@ -3,7 +3,7 @@ title: Setting up your OS for development on MacOS
 description: This section provides a step-by-step guide for setting up your development environment on Mac.
 ---
 
-To develop with MonoGame in C#, you will need to install the .NET SDK. As of MonoGame 3.8.4.1 the recommended version is .NET 9.
+To develop with MonoGame in C#, you will need to install the .NET SDK. As of MonoGame {{mgVersion}} the recommended version is .NET 9.
 
 > [!TIP]
 > You can still continue to use .NET 8 if you wish, you will just need to downgrade your client project .NET version in the `csproj` setup for your project (if using the default templates)
diff --git a/articles/getting_started/1_setting_up_your_os_for_development_ubuntu.md b/articles/getting_started/1_setting_up_your_os_for_development_ubuntu.md
@@ -6,7 +6,7 @@ description: This section provides a step-by-step guide for setting up your deve
 > [!TIP]
 > The minimum version of Ubuntu that is supported by MonoGame is `20.04`.
 
-To develop with MonoGame in C#, you will need to install the .NET SDK. As of MonoGame 3.8.4.1 the minimum supported version is .NET 9.
+To develop with MonoGame in C#, you will need to install the .NET SDK. As of MonoGame {{mgVersion}} the minimum supported version is .NET 9.
 
 ## Install .NET 9 SDK
 
diff --git a/articles/getting_started/1_setting_up_your_os_for_development_windows.md b/articles/getting_started/1_setting_up_your_os_for_development_windows.md
@@ -3,7 +3,7 @@ title: Setting up your OS for development on Windows
 description: This section provides a step-by-step guide for setting up your development environment on Windows.
 ---
 
-To develop with MonoGame in C#, you must install the .NET SDK. As of MonoGame 3.8.4.1 the minimum supported version is .NET 9.
+To develop with MonoGame in C#, you must install the .NET SDK. As of MonoGame {{mgVersion}} the minimum supported version is .NET 9.
 
 > [!IMPORTANT]
 > If your chosen IDE for development is [Visual Studio](https://visualstudio.microsoft.com/) then you can skip this step as .NET 8 is included with the Visual Studio Installer.
diff --git a/articles/getting_to_know/howto/HowTo_Install_Preview_Release.md b/articles/getting_to_know/howto/HowTo_Install_Preview_Release.md
@@ -24,8 +24,8 @@ To use the preview packages delivered via NuGet you need to update or replace yo
 The simplest way is from the command line in the folder where your `csproj` is located (if you have multiple projects, please repeat for each) using the following syntax:
 
 ```dotnetcli
-dotnet add package MonoGame.Framework.DesktopGL -v 3.8.4-preview.1
-dotnet add package MonoGame.Content.Builder.Task -v 3.8.4-preview.1
+dotnet add package MonoGame.Framework.DesktopGL -v {{mgDevelopVersion}}
+dotnet add package MonoGame.Content.Builder.Task -v {{mgDevelopVersion}}
 ```
 
 **Replacing the preview version with the specific version you wish to install.**
@@ -42,11 +42,11 @@ To ensure symmetry between the project version and the Content Pipeline Editor (
 This is simply a matter of updating the tools references, again from the command line in the projects folder, as follows:
 
 ```dotnetcli
-dotnet tool install dotnet-mgcb --version 3.8.4-preview.1
-dotnet tool install dotnet-mgcb-editor --version 3.8.4-preview.1
-dotnet tool install dotnet-mgcb-editor-linux --version 3.8.4-preview.1
-dotnet tool install dotnet-mgcb-editor-windows --version 3.8.4-preview.1
-dotnet tool install dotnet-mgcb-editor-mac --version 3.8.4-preview.1
+dotnet tool install dotnet-mgcb --version {{mgDevelopVersion}}
+dotnet tool install dotnet-mgcb-editor --version {{mgDevelopVersion}}
+dotnet tool install dotnet-mgcb-editor-linux --version {{mgDevelopVersion}}
+dotnet tool install dotnet-mgcb-editor-windows --version {{mgDevelopVersion}}
+dotnet tool install dotnet-mgcb-editor-mac --version {{mgDevelopVersion}}
 ```
 
 **Replacing the preview version with the specific version you wish to install.**
@@ -65,7 +65,7 @@ This step is optional, if you intend to generate a new project using the latest
 1. Simply run the following from the command line:
 
 ```dotnetcli
-dotnet new install MonoGame.Templates.CSharp::3.8.4-preview.1
+dotnet new install MonoGame.Templates.CSharp::{{mgDevelopVersion}}
 ```
 
 **Replacing the preview version of MonoGame at the end of the command with the specific version you wish to install.**
@@ -77,7 +77,7 @@ At this time, the Visual Studio marketplace does not support preview versions of
 The Extension can be downloaded from the latest `GitHub Actions` build used to generate the preview build.
 
 1. Go to the [MonoGame GitHub repository](https://github.com/MonoGame/MonoGame/actions) and select the "Actions" tab.
-1. Find the build with the associated tag, e.g. [`v3.8.4-preview.1`](https://github.com/MonoGame/MonoGame/actions/runs/14713318149)
+1. Find the build with the associated tag, e.g. [`{{mgDevelopVersion}}`](https://github.com/MonoGame/MonoGame/actions/runs/14713318149)
 1. In the `Artifacts` for the build, you should see the extensions installer `MonoGame.Templates.VSExtension.vsix`
 1. Click on the "Download Icon" on the far right-hand side of the row.
 1. Once downloaded, run the `vsix` which will update your installation of the extensions package.
diff --git a/articles/migration/migrate_38.md b/articles/migration/migrate_38.md
@@ -1,6 +1,6 @@
 ---
 title: Upgrading MonoGame from 3.8.x to latest
-description: A guide on upgrading a MonoGame v3.8 project to the current 3.8.4.1+ releases of MonoGame.
+description: A guide on upgrading a MonoGame v3.8 project to the current {{mgVersion}}+ releases of MonoGame.
 ---
 
 Upgrading existing projects from earlier 3.8 releases should be straightforward for most platforms.
@@ -10,7 +10,7 @@ Upgrading existing projects from earlier 3.8 releases should be straightforward
 
 - The critical difference from pre 3.8.2 builds, [is that the MGCB Editor is no longer a global .NET tool](#addupdate-dotnet-toolsjson-configuration) and the MGCB editor is now included as part of the specific project through the use of the dotnet tooling configuration `dotnet-tools.json` file located in the `.config` folder in your solution/project.
 
-- The major difference from 3.8.4 onwards is that we recommend using .NET 9 in your client project, but it is not mandatory, we are also simplifying the `csproj` configuration to reduce management for developers from 3.8.4.1.
+- The major difference from {{mgVersion}} onwards is that we recommend using .NET 9 in your client project, but it is not mandatory, we are also simplifying the `csproj` configuration to reduce management for developers from {{mgVersion}}.
 
     > For iOS/Android however, DotNet 9 at a minimum is Mandatory, [see details here](#iosipados-and-android-considerations).
 
@@ -58,8 +58,8 @@ Make sure you update the MonoGame references to the latest version, this can be
 - Use the [Updating NuGet package dependencies](../getting_to_know/howto/HowTo_Install_Preview_Release.md#updating-nuget-package-dependencies) documentation as part of the "Preview Release installation instructions", which states you should run the following commands (the example is for `DesktopGL`, use other platforms accordingly):
 
     ```dotnetcli
-    dotnet add package MonoGame.Framework.DesktopGL -v 3.8.4.1
-    dotnet add package MonoGame.Content.Builder.Task -v 3.8.4.1
+    dotnet add package MonoGame.Framework.DesktopGL -v {{mgVersion}}
+    dotnet add package MonoGame.Content.Builder.Task -v {{mgVersion}}
     ```
 
     > [!NOTE]
@@ -95,31 +95,31 @@ or alternatively you can do the following:
   "isRoot": true,
   "tools": {
     "dotnet-mgcb": {
-      "version": "3.8.4.1",
+      "version": "{{mgVersion}}",
       "commands": [
         "mgcb"
       ]
     },
     "dotnet-mgcb-editor": {
-      "version": "3.8.4.1",
+      "version": "{{mgVersion}}",
       "commands": [
         "mgcb-editor"
       ]
     },
     "dotnet-mgcb-editor-linux": {
-      "version": "3.8.4.1",
+      "version": "{{mgVersion}}",
       "commands": [
         "mgcb-editor-linux"
       ]
     },
     "dotnet-mgcb-editor-windows": {
-      "version": "3.8.4.1",
+      "version": "{{mgVersion}}",
       "commands": [
         "mgcb-editor-windows"
       ]
     },
     "dotnet-mgcb-editor-mac": {
-      "version": "3.8.4.1",
+      "version": "{{mgVersion}}",
       "commands": [
         "mgcb-editor-mac"
       ]
diff --git a/articles/migration/updating_versions.md b/articles/migration/updating_versions.md
@@ -62,7 +62,7 @@ dotnet restore
 Regardless of the development environment, users will need to update the dotnet tools manifest file manually to use the newest version of the *MonoGame Content Builder*. To do this:
 
 1. Open the *.config/dotnet-tools.json* manifest file located in the project root directory
-2. Update the version specified for each tool to the current version of MonoGame (currently this is `3.8.4`).
+2. Update the version specified for each tool to the current version of MonoGame (currently this is `{{mgVersion}}`).
 3. Save the changes
 
 Once these changes are made, open a command prompt or terminal at the root of the project directory and enter the following commands
