You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 16/umbraco-deploy/release-notes.md
+36-1Lines changed: 36 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
description: Get an overview of the things changed and fixed in each version of Umbraco Deploy.
3
3
---
4
4
5
-
# Release notes
5
+
# Release Notes
6
6
7
7
In this section we have summarised the changes to Umbraco Deploy and [Deploy Contrib](https://github.com/umbraco/Umbraco.Deploy.Contrib) released in each version. Each version is presented with a link to the [Deploy issue tracker](https://github.com/umbraco/Umbraco.Deploy.Issues/issues) showing a list of issues resolved in the release. We also link to the individual issues themselves from the detail.
8
8
@@ -16,6 +16,25 @@ If you are upgrading to a new major version you can find the details about the b
16
16
17
17
This section contains the release notes for Umbraco Deploy 15 including all changes for this version.
* Add `deployEntityTypeMapping` manifest to allow mapping client-side entity types (used in workspaces and routes) to their server-side entity types (used in UDIs, artifacts, and service connectors)
36
+
* Use default `TryParseUdiRangeFromNodeId` implementation for internally registered entity types
Copy file name to clipboardExpand all lines: 16/umbraco-deploy/upgrades/version-specific.md
+42-4Lines changed: 42 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,14 +21,52 @@ Version 16 contains breaking changes. The breaking changes appear in areas relat
21
21
22
22
#### Entity type registration
23
23
24
-
Entity type registration is simplified by removing client-side concerns from the server and aligning built-in and custom Umbraco CMS entities (like Forms and Commerce).
24
+
Entity type registration is simplified by removing client-side concerns from the server and aligning built-in Umbraco CMS and custom entities (like Forms and Commerce).
25
25
26
26
*`IDiskEntityService.RegisterDiskEntityType(...)` - This now only requires the entity type, removing the `name`, `isUmbracoEntity` and `installedUdisGetter` parameters.
27
27
*`ITransferEntityService.RegisterTransferEntityType(...)` - This is also simplified, removing the `name`, `isUmbracoEntity`, `treeAlias`, `matchesRoutePath`, `matchesNodeId` and `entitiesGetter` parameters.
28
28
29
-
The name was only used in the backoffice, for example, to group items in the transfer queue and schema comparison dashboard. It now uses localizations (`deploy_entityTypes_{entityType}` or `general_{entityType}`), falling back to the plain entity type.
30
-
31
-
The `isUmbracoEntity` flag was used in the schema comparison dashboard and for setting signatures to fetch entities differently from custom ones. Making `installedUdisGetter` and `entitiesGetter` mandatory could fetch these items, but this is already possible via service connectors (`IServiceConnector.GetRangeAsync()` and `IServiceConnector.GetArtifact()`).
29
+
The name was only used in the backoffice, for example, to group items in the transfer queue and schema comparison dashboard. It now uses localizations (`deploy_entityTypes_{entityType}` or `general_{entityType}`), falling back to the plain entity type if no translation is provided.
30
+
31
+
The `isUmbracoEntity` flag was used when fetching entities in the schema comparison dashboard and for setting signatures. This could only be enabled for built-in Umbraco entities directly supported by Deploy. Custom entities required providing the `installedUdisGetter` or `entitiesGetter` parameter for these features to work correctly. However, getting all entities is already possible via the service connectors (`IServiceConnector.GetRangeAsync()` and `IServiceConnector.GetArtifact()`), making these parameters redundant.
32
+
33
+
The `treeAlias`, `matchesRoutePath`, and `matchesNodeId` parameters are removed because the client-side already tracks the entity types. It's recommended to use the same entity types on both the client (in workspaces and routes) and the server (in UDIs, artifacts, and service connectors). If different, Deploy supports mapping the client-side entity types to their server-side counterpart using a `deployEntityTypeMapping` manifest, as shown in the following example:
Copy file name to clipboardExpand all lines: 16/umbraco-forms/release-notes.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,6 +50,18 @@ This section contains the release notes for Umbraco Forms 16 including all chang
50
50
51
51
This Deploy add-on adds support for transferring, restoring, exporting and importing (including migrating between major versions) of Umbraco Forms data.
52
52
53
+
### 16.0.0 (June 12th 2025)
54
+
55
+
* Update Forms and Deploy dependencies to 16.0.0
56
+
57
+
### 16.0.0-rc5 (June 10th 2025)
58
+
59
+
* Update Forms and Deploy dependencies to 16.0.0-rc5
60
+
61
+
### 16.0.0-rc4 (June 10th 2025)
62
+
63
+
* Update Forms and Deploy dependencies to 16.0.0-rc4
64
+
53
65
### 16.0.0-rc3 (June 3rd 2025)
54
66
55
67
* Update Forms and Deploy dependencies to 16.0.0-rc3
0 commit comments