Added release notes and documentation updates for Deploy 4.9.3 10.3.3, 12.1.3 13.0.3.

10/umbraco-deploy/getting-started/deploy-settings.md

@@ -53,6 +53,8 @@ For illustration purposes, the following structure represents the full set of op
             "TransferFormsAsContent": true,
             "TransferDictionaryAsContent": false,
             "IgnoreMissingLanguagesForDictionaryItems": false,
+            "SetEmptyDictionaryItemsOnTransfer": true,
+            "IgnoreMissingLanguagesForDictionaryItems": false,
             "AllowMembersDeploymentOperations": "None",
             "TransferMemberGroupsAsContent": false,
             "ExportMemberGroups": true,
@@ -200,6 +202,14 @@ If you have deleted languages that have already existing translations, you may w
 
 When this is in place a translation for a language that doesn't exist in the target environment will be ignored. A warning message will be output to the log.
 
+### SetEmptyDictionaryItemsOnTransfer
+
+When deploying dictionary items, Umbraco Deploy follows the approach used for all content, emptying values that are transferred and set.
+
+If you transfer a dictionary item with an empty translation to another environment that already contains a translation, it will be overwritten.
+
+Set this value to `false` to not overwrite already populated values with empty strings.
+
 ## AllowMembersDeploymentOperations and TransferMemberGroupsAsContent
 
 As of version 9.3.0, it's also possible to transfer members and member groups via the back-office between environments. This is disabled by default as a deliberate decision to make use of the feature needs to be taken, as for most installations it will make sense to have member data created and managed only in production. There are obvious potential privacy concerns to consider too. However, if being able to deploy and restore this information between environments makes sense for the specific workflow of your project, it's a supported scenario.

10/umbraco-deploy/release-notes.md

@@ -21,6 +21,12 @@ This section contains the release notes for Umbraco Deploy 4 and 10 including al
 
 <summary>Version 10</summary>
 
+[**10.3.3**](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F10.3.3) **(January 16th 2024)**
+
+* Added configurable option to avoid overwriting of dictionary items with empty values [#191](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/191)
+    * For more details see the page on [Deploy's settings](./getting-started/deploy-settings.md).
+* Fixed regression issue with transfer of date values.
+
 [**10.3.2**](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F10.3.2) **(January 9th 2024)**
 
 * Fixed issue with transfer of content using language variants [#193](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/193)
@@ -185,6 +191,12 @@ This section contains the release notes for Umbraco Deploy 4 and 10 including al
 
 <summary>Version 4</summary>
 
+[**4.9.3**](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F4.9.3) **(January 16th 2024)**
+
+* Added configurable option to avoid overwriting of dictionary items with empty values [#191](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/191)
+    * For more details see the page on [Deploy's settings](./getting-started/deploy-settings.md).
+* Fixed regression issue with transfer of date values.
+
 [**4.9.2**](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F4.9.2) **(January 9th 2024)**
 
 * Fixed issue with transfer of content using language variants [#193](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/193)

12/umbraco-deploy/getting-started/deploy-settings.md

@@ -55,6 +55,7 @@ For illustration purposes, the following structure represents the full set of op
             "TransferFormsAsContent": true,
             "TransferDictionaryAsContent": false,
             "IgnoreMissingLanguagesForDictionaryItems": false,
+            "SetEmptyDictionaryItemsOnTransfer": true,
             "AllowMembersDeploymentOperations": "None",
             "TransferMemberGroupsAsContent": false,
             "ExportMemberGroups": true,
@@ -220,6 +221,14 @@ If you have deleted languages that have already existing translations, you may w
 
 When this is in place a translation for a language that doesn't exist in the target environment will be ignored. A warning message will be output to the log.
 
+### SetEmptyDictionaryItemsOnTransfer
+
+When deploying dictionary items, Umbraco Deploy follows the approach used for all content, emptying values that are transferred and set.
+
+If you transfer a dictionary item with an empty translation to another environment that already contains a translation, it will be overwritten.
+
+Set this value to `false` to not overwrite already populated values with empty strings.
+
 ## AllowMembersDeploymentOperations and TransferMemberGroupsAsContent
 
 It's also possible to transfer members and member groups via the backoffice between environments. This is disabled by default as a deliberate decision to make use of the feature needs to be taken, as for most installations it will make sense to have member data created and managed only in production. There are obvious potential privacy concerns to consider too. However, if being able to deploy and restore this information between environments makes sense for the specific workflow of your project, it's a supported scenario.

12/umbraco-deploy/release-notes.md

@@ -17,7 +17,13 @@ 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 12 including all changes for this version.
 
-#### [**12.2.2**](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F12.2.2) **(January 9th 2023)**
+#### [**12.2.3**](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F12.2.3) **(January 16th 2024)**
+
+* Added configurable option to avoid overwriting of dictionary items with empty values [#191](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/191)
+    * For more details see the page on [Deploy's settings](./getting-started/deploy-settings.md).
+* Fixed regression issue with transfer of date values.
+
+#### [**12.2.2**](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F12.2.2) **(January 9th 2024)**
 
 * Fixed issue with transfer of content using language variants [#193](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/193)
 

13/umbraco-deploy/getting-started/deploy-settings.md

@@ -55,6 +55,8 @@ For illustration purposes, the following structure represents the full set of op
             "TransferFormsAsContent": true,
             "TransferDictionaryAsContent": false,
             "IgnoreMissingLanguagesForDictionaryItems": false,
+            "SetEmptyDictionaryItemsOnTransfer": true,
+            "IgnoreMissingLanguagesForDictionaryItems": false,
             "AllowMembersDeploymentOperations": "None",
             "TransferMemberGroupsAsContent": false,
             "ExportMemberGroups": true,
@@ -214,6 +216,14 @@ If you have deleted languages that have already existing translations, you may w
 
 When this is in place a translation for a language that doesn't exist in the target environment will be ignored. A warning message will be output to the log.
 
+### SetEmptyDictionaryItemsOnTransfer
+
+When deploying dictionary items, Umbraco Deploy follows the approach used for all content, emptying values that are transferred and set.
+
+If you transfer a dictionary item with an empty translation to another environment that already contains a translation, it will be overwritten.
+
+Set this value to `false` to not overwrite already populated values with empty strings.
+
 ### AllowMembersDeploymentOperations and TransferMemberGroupsAsContent
 
 It's also possible to transfer members and member groups via the backoffice between environments. This is disabled by default as a deliberate decision to make use of the feature needs to be taken, as for most installations it will make sense to have member data created and managed only in production. There are obvious potential privacy concerns to consider too. However, if being able to deploy and restore this information between environments makes sense for the specific workflow of your project, it's a supported scenario.

13/umbraco-deploy/release-notes.md

@@ -17,6 +17,12 @@ 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 13 including all changes for this version.
 
+#### [**13.0.3**](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.0.3) **(January 16th 2024)**
+
+* Added configurable option to avoid overwriting of dictionary items with empty values [#191](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/191)
+    * For more details see the page on [Deploy's settings](./getting-started/deploy-settings.md).
+* Fixed regression issue with transfer of date values.
+
 #### [**13.0.2**](https://github.com/umbraco/Umbraco.Deploy.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.0.2) **(January 9th 2024)**
 
 * Fixed issue with transfer of content using language variants [#193](https://github.com/umbraco/Umbraco.Deploy.Issues/issues/193)