diff --git a/13/umbraco-engage/release-notes.md b/13/umbraco-engage/release-notes.md
index bbe02c34f65..304cea84359 100644
--- a/13/umbraco-engage/release-notes.md
+++ b/13/umbraco-engage/release-notes.md
@@ -13,3 +13,22 @@ When upgrading to a major version, be sure to look at the breaking changes outli
 {% endhint %}
 
 ## Release History
+
+This section contains the release notes for Umbraco Engage 13 including all changes for this version.
+
+#### **[13.2.0](https://www.nuget.org/packages/Umbraco.Engage/13.2.0) (January 21st 2025)**
+* Added Razor Class Library support for Engage, removing physical backoffice, views and assets files from development projects.
+* Resolved the issue where accessing the backoffice through domains with "www." would display as invalid on the start dashboard.
+* Resolved the issue where logging into Umbraco Cloud through an Identity Provider would reset the Engage analytics cookie.
+* Resolved the issue that would display incorrect goal performances in A/B Tests.
+* Improved error indication in case Engage fails to install.
+
+#### **[13.1.0](https://www.nuget.org/packages/Umbraco.Engage/13.1.0) (December 9th 2024)**
+* Introduced the Last Attribution Model when assigning pageviews to campaigns.
+* Optimized A/B Testing Dashboard performance by making use of reporting instead of real-time data.
+* Resolved the issue where Customer Journey Step Scores were incorrectly assigned.
+* Added validation for triggering custom goals on supported pageviews.
+
+#### **[13.0.0](https://www.nuget.org/packages/Umbraco.Engage/13.0.0) (November 7th 2024)**
+* Rebranded uMarketingSuite to Umbraco Engage.
+* Upgraded all dependencies to the latest versions.
diff --git a/13/umbraco-engage/upgrading/upgrade-umbraco-engage.md b/13/umbraco-engage/upgrading/upgrade-umbraco-engage.md
index 10b19c289a9..16de9bc4b0f 100644
--- a/13/umbraco-engage/upgrading/upgrade-umbraco-engage.md
+++ b/13/umbraco-engage/upgrading/upgrade-umbraco-engage.md
@@ -37,13 +37,14 @@ When the task completes, open the **.csproj** file to make sure the package refe
 
 If you are using one or more of the below sub-packages, they also need to be upgraded as well:
 
-| Sub-package | Description |
-| -- | -- |
-| Umbraco.Engage.Core | Core Engage functionality that doesn't require any infrastructure-specific dependencies. |
+| Sub-package                   | Description                                                                              |
+|-------------------------------|------------------------------------------------------------------------------------------|
+| Umbraco.Engage.Core           | Core Engage functionality that doesn't require any infrastructure-specific dependencies. |
 | Umbraco.Engage.Infrastructure | Infrastructure-specific project containing implementations of core Engage functionality. |
-| Umbraco.Engage.Web | The core Engage logic that requires a web context. |
-| Umbraco.Engage.Data | |
-| Umbraco.Engage.Common | |
-| Umbraco.Engage.Forms | A package that extends Umbraco Engage with Umbraco Forms. |
-| Umbraco.Engage.Headless | A package that adds headless functionality to Umbraco Engage. |
-| Umbraco.Engage.Commerce | A package that extends Umbraco Engage with Umbraco Commerce. |
+| Umbraco.Engage.Web            | The core Engage logic that requires a web context.                                       |
+| Umbraco.Engage.Data           | The data connectivity layer for Engage.                                                  |
+| Umbraco.Engage.Common         | The shared utility library for Engage.                                                   |
+| Umbraco.Engage.StaticAssets   | The Static Assets library for Engage.                                                    |
+| Umbraco.Engage.Forms          | A package that extends Umbraco Engage with Umbraco Forms.                                |
+| Umbraco.Engage.Headless       | A package that adds headless functionality to Umbraco Engage.                            |
+| Umbraco.Engage.Commerce       | A package that extends Umbraco Engage with Umbraco Commerce.                             |
diff --git a/13/umbraco-engage/upgrading/version-specific-upgrade-notes.md b/13/umbraco-engage/upgrading/version-specific-upgrade-notes.md
index ef1ef356c01..f4454d074e8 100644
--- a/13/umbraco-engage/upgrading/version-specific-upgrade-notes.md
+++ b/13/umbraco-engage/upgrading/version-specific-upgrade-notes.md
@@ -1,5 +1,5 @@
 ---
-description: Version specific documentation for upgrading to new major versions of Umbraco Engage.
+description: Version-specific documentation for upgrading to new major versions of Umbraco Engage.
 ---
 
 # Version Specific Upgrade Notes
@@ -11,3 +11,23 @@ When upgrading to a new minor or patch version, learn about the changes in the [
 {% endhint %}
 
 ## Breaking changes
+#### v13.2.0
+Introduced Razor Class Library support to serve static files for Engage, removing physical backoffice, views, and assets files from development projects.
+
+While this is not considered a breaking change, it is recommended that such folders be removed from the project to avoid conflicts in the future.
+
+The following folders should be manually removed from your project upon updating:
+
+  * `App_Plugins\Umbraco.Engage`
+  * `Assets\Umbraco.Engage`
+  * `Views\Partials\Umbraco.Engage`
+
+Health checks have been added to verify whether these folders are present in your project. If they are, you will receive a warning in the Health Check dashboard.
+
+The above only applies to the `Umbraco.Engage` package. Any addons like `Umbraco.Engage.Forms` will still have physical files in your project in this version.
+
+#### v13.0.0 (Umbraco Engage Launch)
+
+Umbraco Engage contains a number of breaking changes from the previous uMarketingSuite product.
+
+See the [Migrate from uMarketingSuite](migrate-from-umarketingsuite) for full details.