From e045c14579141ba4737499792962d8481a411ada Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 6 May 2025 07:58:21 +0200 Subject: [PATCH 1/3] Further details of 16 breaking changes --- .../upgrading/version-specific/README.md | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md b/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md index a973e25fbdb..e5bf6f07324 100644 --- a/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md +++ b/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md @@ -31,6 +31,26 @@ When upgrading to Umbraco 16, any data types using TinyMCE will be migrated to u To continue to use TinyMCE, a third-party package must be installed prior to the upgrade. This will disable the migration and allow you to continue with TinyMCE. +**Updated dependencies** + +As is usual for a major upgrade, we've taken the opportunity to update all the dependencies Umbraco takes on the server and client to their latest, compatible versions. This had very little impact on the code of Umbraco itself, so we don't expect this to affect upgraded customer projects. + +The specific dependency updates made for Umbraco 16 can be found in these PRs: for [server-side](https://github.com/umbraco/Umbraco-CMS/pull/19117) and [client-side](https://github.com/umbraco/Umbraco-CMS/pull/19121) libraries. + +**Other breaking changes** + +Other than the TinyMCE removal, breaking changes should be minimal in Umbraco 16. On the server-side, we've mostly limited such changes to the removal of already obsolete constructors and methods. + +Client-side there are a few things to look out for if you've built extensions to the backoffice: + +- When consuming contexts, an `undefined` response will be resolved when the context can't be provided or the host is disconnected. See [PR 19113](https://github.com/umbraco/Umbraco-CMS/pull/19113) for more information. + +- Similarly, consuming a context as a promise can result in a promise rejection and getting a context can result in an undefined response. See [PR 18611](https://github.com/umbraco/Umbraco-CMS/pull/18611) for more information. + +- When making calls to retrieve data from the server, if you used either of Umbraco's helper methods `tryExecute` or `tryExecuteAndNotify`, then you need to adjust your code slightly. `tryExecuteAndNotify` is obsolete, and `tryExecute` takes the 'host' as the first argument. See [PR 18939](https://github.com/umbraco/Umbraco-CMS/pull/18939) for more information. + +The full details of breaking changes can be found from [this list of labelled PRs](https://github.com/umbraco/Umbraco-CMS/pulls?q=is:pr+label:category/breaking+is:closed+label:release/16.0.0). +
From a8806c137dfc2346394f31916fbcb20a150200fa Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 6 May 2025 08:08:19 +0200 Subject: [PATCH 2/3] Linting --- .../fundamentals/setup/upgrading/version-specific/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md b/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md index e5bf6f07324..4644ce524e2 100644 --- a/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md +++ b/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md @@ -33,7 +33,7 @@ To continue to use TinyMCE, a third-party package must be installed prior to the **Updated dependencies** -As is usual for a major upgrade, we've taken the opportunity to update all the dependencies Umbraco takes on the server and client to their latest, compatible versions. This had very little impact on the code of Umbraco itself, so we don't expect this to affect upgraded customer projects. +As is usual for a major upgrade, we've taken the opportunity to update the dependencies Umbraco takes to their latest, compatible versions. This had little impact on the code of Umbraco itself, so we don't expect this to affect upgraded customer projects. The specific dependency updates made for Umbraco 16 can be found in these PRs: for [server-side](https://github.com/umbraco/Umbraco-CMS/pull/19117) and [client-side](https://github.com/umbraco/Umbraco-CMS/pull/19121) libraries. From 197949230556580533c981700c81ab7b0c2b226d Mon Sep 17 00:00:00 2001 From: Andy Butland Date: Tue, 6 May 2025 08:44:43 +0200 Subject: [PATCH 3/3] Apply suggestions from code review Co-authored-by: sofietoft --- .../fundamentals/setup/upgrading/version-specific/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md b/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md index 4644ce524e2..a37a7531e90 100644 --- a/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md +++ b/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md @@ -33,13 +33,13 @@ To continue to use TinyMCE, a third-party package must be installed prior to the **Updated dependencies** -As is usual for a major upgrade, we've taken the opportunity to update the dependencies Umbraco takes to their latest, compatible versions. This had little impact on the code of Umbraco itself, so we don't expect this to affect upgraded customer projects. +As is usual for a major upgrade, the dependencies Umbraco takes have been updated to their latest, compatible versions. This had little impact on the code of Umbraco itself, so we don't expect this to affect upgraded customer projects. The specific dependency updates made for Umbraco 16 can be found in these PRs: for [server-side](https://github.com/umbraco/Umbraco-CMS/pull/19117) and [client-side](https://github.com/umbraco/Umbraco-CMS/pull/19121) libraries. **Other breaking changes** -Other than the TinyMCE removal, breaking changes should be minimal in Umbraco 16. On the server-side, we've mostly limited such changes to the removal of already obsolete constructors and methods. +Other than the TinyMCE removal, breaking changes are minimal in Umbraco 16. On the server side, changes are limited to removing already obsolete constructors and methods. Client-side there are a few things to look out for if you've built extensions to the backoffice: