From 5d575f61b98effc441903ec83c87ea934a9925c0 Mon Sep 17 00:00:00 2001 From: Ronald Barendse Date: Mon, 2 Jun 2025 10:12:36 +0200 Subject: [PATCH 1/5] Remove outdated/unused 'Test the Release Candidate' page --- .../test-the-release-candidate.md | 38 ------------------- .../test-the-release-candidate.md | 38 ------------------- .../test-the-release-candidate.md | 38 ------------------- .../test-the-release-candidate.md | 38 ------------------- 4 files changed, 152 deletions(-) delete mode 100644 13/umbraco-deploy/test-the-release-candidate.md delete mode 100644 14/umbraco-deploy/test-the-release-candidate.md delete mode 100644 15/umbraco-deploy/test-the-release-candidate.md delete mode 100644 16/umbraco-deploy/test-the-release-candidate.md diff --git a/13/umbraco-deploy/test-the-release-candidate.md b/13/umbraco-deploy/test-the-release-candidate.md deleted file mode 100644 index 4796a46c231..00000000000 --- a/13/umbraco-deploy/test-the-release-candidate.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -description: >- - This article will cover in detail how you can try out and test the Release - Candidate (RC) of Umbraco Deploy version 12. ---- - -# Test the Release Candidate - -## Prerequisites - -* Umbraco 12 RC project - -## Getting started with the RC - -To get started working with the Umbraco Deploy release candidate, follow the steps below using the Command Line Interface (CLI): - -1. Navigate your Umbraco project folder: - * ``` - cd TheNameOfYourUmbracoProject - ``` -2. Install/Update Umbraco Deploy: - * ```aspnet - dotnet add package Umbraco.Deploy.OnPrem --version 12.0.0-rc1 - ``` -3. Build the project by running the `dotnet build` command in the project folder -4. Run the project using the `dotnet run` command - -This will boot the project and write the log to the console. The project is now running with Deploy installed. - -{% hint style="info" %} -It is also possible to install the Umbraco Deploy RC using the NuGet Package Manager in Visual Studio. - -Remember to enable **pre-releases**. -{% endhint %} - -## How to provide feedback - -If you find issues that are not already [reported](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aopen+is%3Aissue+label%3Aproject%2Fv12+), please report them on the Umbraco Deploy [GitHub tracker](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/new?assignees=\&labels=\&projects=\&template=1\_Bug.md). diff --git a/14/umbraco-deploy/test-the-release-candidate.md b/14/umbraco-deploy/test-the-release-candidate.md deleted file mode 100644 index 4796a46c231..00000000000 --- a/14/umbraco-deploy/test-the-release-candidate.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -description: >- - This article will cover in detail how you can try out and test the Release - Candidate (RC) of Umbraco Deploy version 12. ---- - -# Test the Release Candidate - -## Prerequisites - -* Umbraco 12 RC project - -## Getting started with the RC - -To get started working with the Umbraco Deploy release candidate, follow the steps below using the Command Line Interface (CLI): - -1. Navigate your Umbraco project folder: - * ``` - cd TheNameOfYourUmbracoProject - ``` -2. Install/Update Umbraco Deploy: - * ```aspnet - dotnet add package Umbraco.Deploy.OnPrem --version 12.0.0-rc1 - ``` -3. Build the project by running the `dotnet build` command in the project folder -4. Run the project using the `dotnet run` command - -This will boot the project and write the log to the console. The project is now running with Deploy installed. - -{% hint style="info" %} -It is also possible to install the Umbraco Deploy RC using the NuGet Package Manager in Visual Studio. - -Remember to enable **pre-releases**. -{% endhint %} - -## How to provide feedback - -If you find issues that are not already [reported](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aopen+is%3Aissue+label%3Aproject%2Fv12+), please report them on the Umbraco Deploy [GitHub tracker](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/new?assignees=\&labels=\&projects=\&template=1\_Bug.md). diff --git a/15/umbraco-deploy/test-the-release-candidate.md b/15/umbraco-deploy/test-the-release-candidate.md deleted file mode 100644 index 4796a46c231..00000000000 --- a/15/umbraco-deploy/test-the-release-candidate.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -description: >- - This article will cover in detail how you can try out and test the Release - Candidate (RC) of Umbraco Deploy version 12. ---- - -# Test the Release Candidate - -## Prerequisites - -* Umbraco 12 RC project - -## Getting started with the RC - -To get started working with the Umbraco Deploy release candidate, follow the steps below using the Command Line Interface (CLI): - -1. Navigate your Umbraco project folder: - * ``` - cd TheNameOfYourUmbracoProject - ``` -2. Install/Update Umbraco Deploy: - * ```aspnet - dotnet add package Umbraco.Deploy.OnPrem --version 12.0.0-rc1 - ``` -3. Build the project by running the `dotnet build` command in the project folder -4. Run the project using the `dotnet run` command - -This will boot the project and write the log to the console. The project is now running with Deploy installed. - -{% hint style="info" %} -It is also possible to install the Umbraco Deploy RC using the NuGet Package Manager in Visual Studio. - -Remember to enable **pre-releases**. -{% endhint %} - -## How to provide feedback - -If you find issues that are not already [reported](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aopen+is%3Aissue+label%3Aproject%2Fv12+), please report them on the Umbraco Deploy [GitHub tracker](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/new?assignees=\&labels=\&projects=\&template=1\_Bug.md). diff --git a/16/umbraco-deploy/test-the-release-candidate.md b/16/umbraco-deploy/test-the-release-candidate.md deleted file mode 100644 index 4796a46c231..00000000000 --- a/16/umbraco-deploy/test-the-release-candidate.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -description: >- - This article will cover in detail how you can try out and test the Release - Candidate (RC) of Umbraco Deploy version 12. ---- - -# Test the Release Candidate - -## Prerequisites - -* Umbraco 12 RC project - -## Getting started with the RC - -To get started working with the Umbraco Deploy release candidate, follow the steps below using the Command Line Interface (CLI): - -1. Navigate your Umbraco project folder: - * ``` - cd TheNameOfYourUmbracoProject - ``` -2. Install/Update Umbraco Deploy: - * ```aspnet - dotnet add package Umbraco.Deploy.OnPrem --version 12.0.0-rc1 - ``` -3. Build the project by running the `dotnet build` command in the project folder -4. Run the project using the `dotnet run` command - -This will boot the project and write the log to the console. The project is now running with Deploy installed. - -{% hint style="info" %} -It is also possible to install the Umbraco Deploy RC using the NuGet Package Manager in Visual Studio. - -Remember to enable **pre-releases**. -{% endhint %} - -## How to provide feedback - -If you find issues that are not already [reported](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aopen+is%3Aissue+label%3Aproject%2Fv12+), please report them on the Umbraco Deploy [GitHub tracker](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/new?assignees=\&labels=\&projects=\&template=1\_Bug.md). From 493a4155aef7189f0cf316cafee4126a6a1f8bfd Mon Sep 17 00:00:00 2001 From: Ronald Barendse Date: Mon, 2 Jun 2025 11:27:57 +0200 Subject: [PATCH 2/5] Add Deploy 16 RC release notes and update version specific upgrade notes --- 16/umbraco-deploy/release-notes.md | 87 +++---------------- .../upgrades/version-specific.md | 34 +++----- 2 files changed, 20 insertions(+), 101 deletions(-) diff --git a/16/umbraco-deploy/release-notes.md b/16/umbraco-deploy/release-notes.md index d145b751b39..61c99f43a52 100644 --- a/16/umbraco-deploy/release-notes.md +++ b/16/umbraco-deploy/release-notes.md @@ -16,93 +16,26 @@ If you are upgrading to a new major version you can find the details about the b This section contains the release notes for Umbraco Deploy 15 including all changes for this version. -### [15.1.0](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F15.1.0) (February 6th 2025) +### [16.0.0-rc2](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F16.0.0) (May 30th 2025) -* All items from 15.1.0-rc1 -* Add user groups to schema comparison +* Compatibility with Umbraco 16.0.0-rc3 +* Rename/add `CancellationToken` parameters and add `ConfigureAwait(false)` to awaits -### [15.1.0-rc1](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F15.1.0) (January 30th 2025) +### [16.0.0-rc1](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F16.0.0) (May 16th 2025) -* Schema cleanup and item actions triggered from Deploy's management dashboard (create or delete UDA files and Umbraco items) -* Allow ignoring dependencies in transfer/restore operations -* Ignore `Dependencies` artifact property when calculating the checksum and fix schema comparison [#246](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/246) -* Add 'Hide up to date' toggle to schema comparison [#245](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/245) -* Fix parsing dictionary item root UDI range from node ID -* Ensure work item references/action results are deallocated (reduces overall memory usage in Deploy) -* Allow disabling warnings as errors on import -* Schema deployment of user groups - -### [15.0.2](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F15.0.2) (December 23rd 2024) - -* Ensure environment-to-environment actions are executed asynchronously on background job (fixes timeout issues on large deployments) [#179](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/179) -* Only require default, allowed and master templates and their associated files to exist (avoids schema mismatches on template changes) [156](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/156) - -### [15.0.1](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F15.0.1) (November 29th 2024) - -* Update documentation links in management dashboard to include major version in the URL -* Add `ValidateDependenciesOnImport` setting to management dashboard -* Fix tree restore for custom entities [#241](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/241) -* Fix import complete heading and description (was using export complete localization keys) -* Disable import button when no file is selected - -### [15.0.0](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F15.0.0) (November 14th 2024) - -* Update CMS dependency to 15.0.0 - -### [15.0.0-rc4](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F15.0.0) (November 13th 2024) - -* Update CMS dependency to 15.0.0-rc4 -* Preview of features and bug fixes due in 13.3 and 14.2: - * Import on startup - * Added `ValidateDependenciesOnImport` setting to disable dependency validation on import - * Support flexible environments on Umbraco Cloud (remove requirement for environment types to be Development, Staging or Live) - -### [15.0.0-rc3](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F15.0.0) (November 7th 2024) - -* Update CMS dependency to 15.0.0-rc3 - -### [15.0.0-rc2](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F15.0.0) (October 24th 2024) - -* Update CMS dependency to 15.0.0-rc2 -* Preview of features and bug fixes due in 13.3 and 14.2: - * Add option to include all schema in a workspace export - * Add option to export from transfer queue - * Fix `BlockValue` obsoleted properties (set GUID keys instead of UDIs and support block level variants) - * Combine migrated grid editor with default Block Grid block configuration (set `RowMinSpan` and `RowMaxSpan` to `1` and `EditorSize` to `medium`) -* Restructure keys and add new UI localizations - -### [15.0.0-rc1](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F15.0.0) (October 11th 2024) - -* Compatibility with Umbraco 15 +* Compatibility with Umbraco 16.0.0-rc2 * See full details of breaking changes under the [Version-specific Upgrade Guide](upgrades/version-specific.md) -* Removed `AcceptInvalidCertificates` setting (configure `DeployHttpClient` typed client instead) -* Removed `RemoteTreeNode` model (use `RemoteTreeEntity` instead) and `TryParseEntityIdFromNodeIdDelegate` (use `TryParseUdiRangeFromNodeIdDelegate` instead) in `DeployTransferRegisteredEntityTypeDetail` -* Added `MigrateAsync(...)` method to `IPropertyTypeMigrator` and updated `PropertyTypeMigratorBase` and implementations to use async instead ## Umbraco.Deploy.Contrib -### [15.0.0](https://github.com/umbraco/Umbraco.Deploy.Contrib/releases/tag/release-15.0.0) (November 14th 2024) - -* Update CMS and Deploy dependencies to 15.0.0 - -### [15.0.0-rc4](https://github.com/umbraco/Umbraco.Deploy.Contrib/releases/tag/release-15.0.0-rc4) (November 13th 2024) - -* Update CMS and Deploy dependencies to 15.0.0-rc4 - -### [15.0.0-rc3](https://github.com/umbraco/Umbraco.Deploy.Contrib/releases/tag/release-15.0.0-rc3) (November 7th 2024) - -* Update CMS and Deploy dependencies to 15.0.0-rc3 - -### [15.0.0-rc2](https://github.com/umbraco/Umbraco.Deploy.Contrib/releases/tag/release-15.0.0-rc2) (October 24th 2024) +### [16.0.0-rc2](https://github.com/umbraco/Umbraco.Deploy.Contrib/releases/tag/release-16.0.0-rc2) (May 30th 2025) -* Update CMS and Deploy dependencies to 15.0.0-rc2 +* Compatibility with Umbraco 16.0.0-rc3 and Deploy 16.0.0-rc2 -### [15.0.0-rc1](https://github.com/umbraco/Umbraco.Deploy.Contrib/releases/tag/release-15.0.0-rc1) (October 14th 2024) +### [16.0.0-rc1](https://github.com/umbraco/Umbraco.Deploy.Contrib/releases/tag/release-16.0.0-rc1) (May 20th 2025) -* Compatibility with Umbraco 15 and Deploy 15 -* Removed obsolete (and unused) legacy `PrevaluePropertyValueArtifactMigratorBase`, `CheckBoxListPropertyValueArtifactMigrator` `DropDownListFlexiblePropertyValueArtifactMigrator` and `RadioButtonListPropertyValueArtifactMigrator` migrators, as they are replaced with `PrevalueArtifactMigrator` and property type migrators that support nested/recursive properties (see PR [#71](https://github.com/umbraco/Umbraco.Deploy.Contrib/pull/71)) -* Removed `MediaPickerDataTypeArtifactMigrator`, as it is replaced with `ReplaceMediaPickerDataTypeArtifactMigrator` and `DefaultLegacyDataTypeConfigurationArtifactMigrator` -* Removed `MultiNodeTreePickerDataTypeArtifactMigrator`, as it is replaced with `DefaultLegacyDataTypeConfigurationArtifactMigrator` +* Compatibility with Umbraco 16.0.0-rc2 and Deploy 16.0.0-rc1 +* Update `TinyMCEv3DataTypeArtifactMigrator` to migrate legacy (v7) Umbraco.TinyMCEv3 to Umbraco.RichText with Tiptap UI editor ## Legacy release notes diff --git a/16/umbraco-deploy/upgrades/version-specific.md b/16/umbraco-deploy/upgrades/version-specific.md index 338197a99f4..33c0eb1e7c6 100644 --- a/16/umbraco-deploy/upgrades/version-specific.md +++ b/16/umbraco-deploy/upgrades/version-specific.md @@ -5,7 +5,7 @@ description: >- # Version Specific Upgrade Details -This article provides specific upgrade documentation for migrating to Umbraco Deploy version 15. +This article provides specific upgrade documentation for migrating to Umbraco Deploy version 16. {% hint style="info" %} If you are upgrading to a minor or patch version, you can find the details about the changes in the [Release Notes](../release-notes.md) article. @@ -13,40 +13,26 @@ If you are upgrading to a minor or patch version, you can find the details about ## Version Specific Upgrade Notes History -Version 15 of Umbraco Deploy has a minimum dependency on Umbraco CMS core of `15.0.0`. It runs on .NET 9. +Version 16 of Umbraco Deploy has a minimum dependency on Umbraco CMS core of `16.0.0`. It runs on .NET 9. ### Breaking changes -Version 15 contains breaking changes. The breaking changes appear in areas related to extending Deploy to support additional entities and property editors. For reference though, the full details are listed here: +Version 16 contains breaking changes. The breaking changes appear in areas related to extending Deploy to support additional entities. For reference though, the full details are listed here: -#### Async methods +#### Entity type registration -Asynchronous methods have been added to the following interfaces: -- `IPropertyTypeMigrator`: - - `MigrateAsync(...)` +The entity type registration has been simplified, removing client-side concerns from the server-side and align behavior between built-in Umbraco CMS entities and custom ones (like Forms and Commerce). -These methods all have a default implementation that forwards the calls to the synchronous methods (to maintain backwards compatibility). The synchronous methods have been obsoleted and Deploy will now always call the new asynchronous methods. Implementations should be updated to start using those instead. +* `IDiskEntityService.RegisterDiskEntityType(...)` - This now only requires the entity type, removing the `name`, `isUmbracoEntity` and `installedUdisGetter` parameters. +* `ITransferEntityService.RegisterTransferEntityType(...)` - This is also simplified, removing the `name`, `isUmbracoEntity`, `treeAlias`, `matchesRoutePath`, `matchesNodeId` and `entitiesGetter` parameters. -- `PropertyTypeMigratorBase` and `GridPropertyTypeMigratorBase`: the synchronous `Migrate(...)` method is obsoleted and causes a compiler error when directly invoked (to avoid potential deadlocks, because it forwards to the asynchronous method using `GetAwaiter().GetResult()`); -- All property type migrator implementations inheriting from the above base classes have been updated to use the asynchronous methods as well. +The name was only used in the backoffice (as friendly entity type name, e.g. to group items in the transfer queue and the schema comparison dashboard), so this is now using localizations (using `deploy_entityTypes_{entityType}` or `general_{entityType}`, falling back to the plain entity type). -#### Removed `AcceptInvalidCertificates` setting - -The `AcceptInvalidCertificates` setting previously configured the `ServicePointManager` to accept all certificates. However, this class is [obsoleted in .NET 9 and no longer affects `HttpClient`](https://learn.microsoft.com/en-us/dotnet/api/system.net.servicepointmanager?view=net-9.0). - -Deploy uses a type of client to make HTTP requests between environments and this client can be configured to accept any certificate: - -```csharp -builder.Services.AddHttpClient().ConfigurePrimaryHttpMessageHandler(() => new HttpClientHandler -{ - // Only use this for testing purposes or if you have other security in place (e.g. only allow environments to connect over an internal network) - ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator -}); -``` +The `isUmbracoEntity` flag was used in the schema comparison dashboard and when setting signatures to get all entities in a different way compared to custom entities. Although we could make the `installedUdisGetter` and `entitiesGetter` parameters mandatory and use those to fetch the required items, this is already possible using the service connectors (using `IServiceConnector.GetRangeAsync()` and `IServiceConnector.GetArtifact()`). ### Dependencies -* Umbraco CMS dependency was updated to `15.0.0`. +* Umbraco CMS dependency was updated to `16.0.0`. ## Legacy version-specific upgrade notes From 9b30bdd68120a57a82eeb77636042dcf504ee68e Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 2 Jun 2025 14:17:21 +0200 Subject: [PATCH 3/5] Update 16/umbraco-deploy/upgrades/version-specific.md --- 16/umbraco-deploy/upgrades/version-specific.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16/umbraco-deploy/upgrades/version-specific.md b/16/umbraco-deploy/upgrades/version-specific.md index 33c0eb1e7c6..1d680ccbe05 100644 --- a/16/umbraco-deploy/upgrades/version-specific.md +++ b/16/umbraco-deploy/upgrades/version-specific.md @@ -21,7 +21,7 @@ Version 16 contains breaking changes. The breaking changes appear in areas relat #### Entity type registration -The entity type registration has been simplified, removing client-side concerns from the server-side and align behavior between built-in Umbraco CMS entities and custom ones (like Forms and Commerce). +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). * `IDiskEntityService.RegisterDiskEntityType(...)` - This now only requires the entity type, removing the `name`, `isUmbracoEntity` and `installedUdisGetter` parameters. * `ITransferEntityService.RegisterTransferEntityType(...)` - This is also simplified, removing the `name`, `isUmbracoEntity`, `treeAlias`, `matchesRoutePath`, `matchesNodeId` and `entitiesGetter` parameters. From ae3953ae6508b24b9f1e747e7efee646fae2746e Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 2 Jun 2025 14:17:28 +0200 Subject: [PATCH 4/5] Update 16/umbraco-deploy/upgrades/version-specific.md --- 16/umbraco-deploy/upgrades/version-specific.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16/umbraco-deploy/upgrades/version-specific.md b/16/umbraco-deploy/upgrades/version-specific.md index 1d680ccbe05..5ced4cf7392 100644 --- a/16/umbraco-deploy/upgrades/version-specific.md +++ b/16/umbraco-deploy/upgrades/version-specific.md @@ -26,7 +26,7 @@ Entity type registration is simplified by removing client-side concerns from the * `IDiskEntityService.RegisterDiskEntityType(...)` - This now only requires the entity type, removing the `name`, `isUmbracoEntity` and `installedUdisGetter` parameters. * `ITransferEntityService.RegisterTransferEntityType(...)` - This is also simplified, removing the `name`, `isUmbracoEntity`, `treeAlias`, `matchesRoutePath`, `matchesNodeId` and `entitiesGetter` parameters. -The name was only used in the backoffice (as friendly entity type name, e.g. to group items in the transfer queue and the schema comparison dashboard), so this is now using localizations (using `deploy_entityTypes_{entityType}` or `general_{entityType}`, falling back to the plain entity type). +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. The `isUmbracoEntity` flag was used in the schema comparison dashboard and when setting signatures to get all entities in a different way compared to custom entities. Although we could make the `installedUdisGetter` and `entitiesGetter` parameters mandatory and use those to fetch the required items, this is already possible using the service connectors (using `IServiceConnector.GetRangeAsync()` and `IServiceConnector.GetArtifact()`). From 65d20964fd3f7d341cbef687455240dedf296a5f Mon Sep 17 00:00:00 2001 From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com> Date: Mon, 2 Jun 2025 14:17:33 +0200 Subject: [PATCH 5/5] Update 16/umbraco-deploy/upgrades/version-specific.md --- 16/umbraco-deploy/upgrades/version-specific.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16/umbraco-deploy/upgrades/version-specific.md b/16/umbraco-deploy/upgrades/version-specific.md index 5ced4cf7392..e283a8c0f7f 100644 --- a/16/umbraco-deploy/upgrades/version-specific.md +++ b/16/umbraco-deploy/upgrades/version-specific.md @@ -28,7 +28,7 @@ Entity type registration is simplified by removing client-side concerns from the 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. -The `isUmbracoEntity` flag was used in the schema comparison dashboard and when setting signatures to get all entities in a different way compared to custom entities. Although we could make the `installedUdisGetter` and `entitiesGetter` parameters mandatory and use those to fetch the required items, this is already possible using the service connectors (using `IServiceConnector.GetRangeAsync()` and `IServiceConnector.GetArtifact()`). +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()`). ### Dependencies