Upgrade your v10 workspace to 2107.3 (or a newer AMP, when available) by merging in the corresponding branch of CoreMedia's Blueprint workspace and follow the release notes as usual. 2107.3+ is the mandatory starting point, prior releases will not work.

Apply the Studio Client workspace conversion tool to your workspace as described in Section 7.2.1, “Converting Studio Client to TypeScript”. This replaces almost all files under apps/studio-client by their TypeScript/npm counterpart. Build this state of the workspace (see Build the Converted Workspace). In most cases, this should succeed without fatal errors (non-fatal type errors are expected). As a smoke test and checkpoint, try to start Studio Client with your customizations (see Start Converted Studio Client). Note that you are still on v10 2107, only that all Studio Client code is now in TypeScript and it is built by pnpm.

Before you can upgrade to v11 (2110), you must ignore-merge CoreMedia Blueprint's branch 2107.3-ts. This tells Git that your workspace has already been converted and ignores all changes that result from converting an unchanged CoreMedia Blueprint workspace. For details see Section 3.6, “Upgrading your Workspace with Git”.

In the Pre-Release, CoreMedia does not provide a Blueprint GitHub branch and thus also no 2107.3-ts branch. Section 3.6, “Upgrading your Workspace with Git” contains instructions how to create such a branch for the Pre-Release.

Remove all components (for example, Optimizely, Aurora B2B) from your workspace, that are no longer supported in CoreMedia Content Cloud v11. This way, you will reduce the number of conflicts when you merge the CMCC v11 workspace. See Section 3.4, “Removing Outdated Components” for details.

Now, merge in CoreMedia Blueprint Branch 2110.1. This may result in merge conflicts and issues where the new major release introduced breaking changes. To resolve these issues, read this document and all applicable release notes for Studio Client carefully. In the workspace, you find documentation of the new command lines to build and watch Studio Client (apps/studio-client/README.md).

When all your customizations work again, you most likely still experience type errors when building the Studio Client workspace, and your TypeScript-capable IDE should also report such errors. You can ignore these non-fatal errors for now, but we recommend fixing them to improve code quality, find bugs and ease maintenance. Section 4 discusses in detail how to fix type errors.