Skip to content

Commit 7fb1f7c

Browse files
authored
Merge pull request #6133 from umbraco/update-to-v14-rc5
update to v14 rc5
2 parents a88d689 + 6b2f5af commit 7fb1f7c

File tree

8 files changed

+23
-9
lines changed

8 files changed

+23
-9
lines changed

14/umbraco-cms/extending/customize-backoffice/development-flow/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,10 +48,10 @@ Umbraco publishes an NPM package called `@umbraco-cms/backoffice` that holds typ
4848
You can install this package by running the command:
4949

5050
```bash
51-
npm install -D @umbraco-cms/backoffice@14.0.0-rc4
51+
npm install -D @umbraco-cms/backoffice@14.0.0-rc5
5252
```
5353

54-
This will add a package to your devDependencies containing the TypeScript definitions for the Umbraco Backoffice. The `-rc4` is the version of the package, which will change as new versions are released.
54+
This will add a package to your devDependencies containing the TypeScript definitions for the Umbraco Backoffice. The `-rc5` is the version of the package, which will change as new versions are released.
5555

5656
It is important that this namespace is ignored in your bundler. If you are using Vite, you can add the following to your `vite.config.ts` file:
5757

14/umbraco-cms/extending/customize-backoffice/development-flow/vite-package-setup.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,12 +53,12 @@ npm install
5353
4. Install the Backoffice package. You can install the package using the following command:
5454

5555
```bash
56-
npm install -D @umbraco-cms/backoffice@14.0.0-rc4
56+
npm install -D @umbraco-cms/backoffice@14.0.0-rc5
5757
```
5858

5959
{% hint style="info" %}
6060
Optionally you can use `--legacy-peer-deps` in the installation command to avoid installing Umbraco´s sub-dependencies like TinyMCE and Monaco Editor:\
61-
`npm install --legacy-peer-deps -D @umbraco-cms/backoffice@14.0.0-rc4`
61+
`npm install --legacy-peer-deps -D @umbraco-cms/backoffice@14.0.0-rc5`
6262

6363
If this is used the Intellisense to those external references will not be available.
6464
{% endhint %}
@@ -104,6 +104,7 @@ npm run build
104104
If you like to continuously work on the package and have each change built, you can add a `watch`script in your `package.json` with `vite build --watch`. The example below indicates where in the structure this change should be implemented:
105105

106106
{% code title="package.json" lineNumbers="true" %}
107+
107108
```json
108109
{
109110
"name": "my-dashboard",
@@ -114,6 +115,7 @@ If you like to continuously work on the package and have each change built, you
114115
},
115116
...
116117
```
118+
117119
{% endcode %}
118120

119121
Then in the terminal, you can run `npm run watch`.
@@ -125,6 +127,7 @@ Declare your package to Umbraco via a file called `umbraco-package.json`. This s
125127
This example declares a Dashboard as part of your Package, using the Vite example element.
126128

127129
{% code title="umbraco-package.json" lineNumbers="true" %}
130+
128131
```json
129132
{
130133
"$schema": "../../umbraco-package-schema.json",
@@ -145,6 +148,7 @@ This example declares a Dashboard as part of your Package, using the Vite exampl
145148
]
146149
}
147150
```
151+
148152
{% endcode %}
149153

150154
{% hint style="info" %}
@@ -156,6 +160,7 @@ Umbraco needs the name of the element that will render as default when our dashb
156160
```ts
157161
export default class MyElement extends LitElement {
158162
```
163+
159164
{% endhint %}
160165

161166
Learn more about the abilities of the manifest file in the [Umbraco Package Manifest](../../property-editors/package-manifest.md) article.

14/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/label-property-configuration.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
# Configuring Block Editor Label Properties
22

3+
{% hint style="warning" %}
4+
This guide is awaiting to be updated as it uses Angular which has been removed from v14.
5+
{% endhint %}
6+
37
When configuring a block, the label property allows you to define a label for the appearance of the Block in the editor. The label can use AngularJS template string syntax to display values of properties. Example: `My Block {{myPropertyAlias}}` will be shown as: `My Block FooBar`.
48

59
You can also use more advanced expressions using AngularJS filters. Example: `{{myPropertyAlias | limitTo:100}}` or for a property using the Richtext editor `{{myPropertyAlias | ncRichText | truncate:true:100}}`.

14/umbraco-cms/fundamentals/setup/install/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ The fastest way to get the latest version of Umbraco up and running is using the
1212
2. Install the Umbraco templates:
1313

1414
```bash
15-
dotnet new install Umbraco.Templates::14.0.0-rc4
15+
dotnet new install Umbraco.Templates::14.0.0-rc5
1616
```
1717

1818
3. Create a new project:

14/umbraco-cms/fundamentals/setup/install/installing-nightly-builds.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ To install the latest nightly version template:
144144
2. Run the following command using the latest version:
145145

146146
```bash
147-
dotnet new install Umbraco.Templates::14.0.0-rc4
147+
dotnet new install Umbraco.Templates::14.0.0-rc5
148148
```
149149

150150
With that, we've successfully installed the latest nightly build of Umbraco.

14/umbraco-cms/fundamentals/setup/upgrading/version-specific/README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -211,6 +211,11 @@ More details and code examples can be found in the [External Login Providers](..
211211

212212
Below you can find the list of breaking changes introduced in Umbraco 14 RC release versions.
213213

214+
**RC 5**
215+
216+
* [Bellissima (frontend/backoffice) changes](https://github.com/umbraco/Umbraco.CMS.Backoffice/releases/tag/v14.0.0-rc5)
217+
* [Backend (CMS) changes](https://github.com/umbraco/Umbraco-CMS/releases/tag/release-14.0.0-rc5)
218+
214219
**RC 4**
215220

216221
* [Bellissima (frontend/backoffice) changes](https://github.com/umbraco/Umbraco.CMS.Backoffice/releases/tag/v14.0.0-rc4)

14/umbraco-cms/reference/management/services/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Below you can find a list of most common services:
3434

3535
## [MediaService](https://apidocs.umbraco.com/v14/csharp/api/Umbraco.Cms.Core.Services.IMediaService.html)
3636

37-
## [MemberGroupService](https://apidocs.umbraco.com/v13/csharp/api/Umbraco.Cms.Core.Services.IMemberGroupService.html)
37+
## [MemberGroupService](https://apidocs.umbraco.com/v14/csharp/api/Umbraco.Cms.Core.Services.IMemberGroupService.html)
3838

3939
## [MemberService](https://apidocs.umbraco.com/v14/csharp/api/Umbraco.Cms.Core.Services.IMemberService.html)
4040

14/umbraco-cms/tutorials/creating-your-first-extension.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -160,10 +160,10 @@ npm install
160160
3. The last thing we need to install now is our Backoffice package. You can install the package using the following command:
161161
162162
```bash
163-
npm install -D @umbraco-cms/backoffice@14.0.0-rc4
163+
npm install -D @umbraco-cms/backoffice@14.0.0-rc5
164164
```
165165
166-
This will add a package to your devDependencies containing the TypeScript definitions for the Umbraco Backoffice. The `-rc4` is the version of the package, which will change as new versions are released.
166+
This will add a package to your devDependencies containing the TypeScript definitions for the Umbraco Backoffice. The `-rc5` is the version of the package, which will change as new versions are released.
167167
168168
{% hint style="warning" %}
169169
If you see any errors during this process, make sure that you have the right tools installed (Node, .NET, and so on). Also, make sure you have followed the steps on how to [Setup Your Development Environment](../extending/customize-backoffice/development-flow/README.md).

0 commit comments

Comments
 (0)