BYO Git GA in 9.24.0 on 28 March 2023

Author: MarkvanMents

content/en/docs/refguide/version-control/_index.md

@@ -19,10 +19,6 @@ Version Control allows you to manage your app development in two ways:
 
 Version control in Mendix is built on top [Git](https://git-scm.com). The concepts will be familiar to seasoned users of these version control systems (VCS). Mendix simplifies the VCS commands by building them into Studio Pro, Studio, and the Developer Portal.
 
-{{% alert color="info" %}}
-Team Server Git was released for GA in version [9.12.0](/releasenotes/studio-pro/9.12/#team-server-git). BYO Git (Bring Your Own) is in Beta since Mendix version [9.6.0](/releasenotes/studio-pro/9.6/#960). For more details, see [Working with Git On-Premises Version Control Server](/refguide/on-premises-git/) in the *Studio Pro Guide*. 
-{{% /alert %}}
-
 ## 2 Concepts {#concepts}
 
 ### 2.1 Team Server {#team-server}

content/en/docs/refguide9/version-control/_index.md

@@ -20,7 +20,7 @@ Version Control allows you to manage your app development in two ways:
 Version control in Mendix is built on top of either [Apache Subversion](https://subversion.apache.org/) or [Git](https://git-scm.com). The concepts will be familiar to seasoned users of these version control systems (VCS). Mendix simplifies the VCS commands by building them into Studio Pro, Studio, and the Developer Portal.
 
 {{% alert color="info" %}}
-Team Server Git was released for GA in version [9.12.0](/releasenotes/studio-pro/9.12/#team-server-git). BYO Git (Bring Your Own) is in Beta since Mendix version [9.6.0](/releasenotes/studio-pro/9.6/#960). For more details, see [Working with Git On-Premises Version Control Server](/refguide9/on-premises-git/) in the *Studio Pro Guide*. 
+Team Server Git was released for GA in version [9.12.0](/releasenotes/studio-pro/9.12/#team-server-git). BYO (Bring Your Own) Git was in Beta from Mendix version [9.6.0](/releasenotes/studio-pro/9.6/#960) and was GA in Mendix version [9.24.0](/releasenotes/studio-pro/9.24/#private-git). For more details, see [Working with Git On-Premises Version Control Server](/refguide9/on-premises-git/) in the *Studio Pro Guide*. 
 {{% /alert %}}
 
 ## 2 Concepts {#concepts}

content/en/docs/releasenotes/feature-release-calendar/_index.md

@@ -76,7 +76,7 @@ If you want to watch the keynote speech in which these announcements were made,
 | --- | --- |
 | Studio Pro modernization | Released for GA on [Sep 28th, 2021](/releasenotes/studio-pro/9.6/#studio-pro-new-design) |
 | Team Server Git (Mendix Cloud) | Released for GA on [Mar 29th, 2022](/releasenotes/studio-pro/9.12/#team-server-git) |
-| BYO Git (Bring Your Own) | Currently in Public Beta<br/>GA: Apr 2023 |
+| BYO Git (Bring Your Own) | Released for GA on [Mar 28th, 2023](/releasenotes/studio-pro/9.24/#private-git) |
 | Studio Pro dark theme | Currently in Public Beta <br />GA: TBD |
 
 ## 8 Data Hub 2.0

content/en/docs/releasenotes/studio-pro/9/9.24.md

@@ -228,7 +228,7 @@ We made a major update to your business events modelling experience:
 * We revised MxAssist Performance Bot best practice [MXP015](/refguide9/performance-best-practices/#mxp015) for XPath ordering to avoid false positives.
 * We extended MxAssist Performance Bot best practice [MXP003](/refguide9/performance-best-practices/#mxp003) for a non-indexed attribute used in sorting to include the Integer type.
 * We added a general note to the MxAssist Performance Bot recommendation pop-up messages.
-* Private Git is now always enabled, so there is no need to enable it in the Studio Pro **Preferences**.
+* <a id="private-git"></a>Private Git is now always enabled, so there is no need to enable it in the Studio Pro **Preferences**.
 * It is no longer possible to create new apps with SVN for the version control. You can still download existing SVN-controlled apps.
 * We added support to [ML Kit](/refguide9/machine-learning-kit/) for importing an ONNX file with all static input shapes but some dynamic output shapes.
 * We aligned the status codes and error messages that a published OData service returns for a number of cases where the resource is either not existing or not accessible. In these cases, we now return the status 404 "resource not found."