Sitecore CLI – Keep this in mind when upgrading from 2.0.0 to 3.0.0
For all of you, who already have a running solution with Sitecore 10 and now want to update to newest 10.1 you will sooner or later come to the point, where yo upgrade Sitecore CLI to the newest
For all of you, who already have a running solution with Sitecore 10 and now want to update to newest 10.1 you will sooner or later come to the point, where yo upgrade Sitecore CLI to the newest version.
If you want to do that, you can simply use the update command in powershell

So far so good. Let’s run our up.ps1 script again to see, if everything is still ok.

And of course it was not. Otherwise this post would not be necessary ^^
When I saw that, I was a bit confused, cause these commands were still available in version 2.0.0. So I wanted to have look at the help of Sitecore CLI

And you see, it is really not available anymore. But on the other side we now have a new command plugin. So this means, Sitecore CLI now can be extended via plugins. So also serialization is a plugin you have to install (In case you update from 2.0.0 to 3.0.0)

In case of an update instead of full installation, your sitecore.json file will most likely look similiar to the one above.
After having a short look at Getting Started example, I got the necessary plugin names, which have to be installed now in my solution. Beside serialization we will also directly install publishing plugin. So let’s install quickly those plugins




After installation of those plugins, you will see, that the commands are back, as we know them from before.

In addition the sitecore.json file has been update to include those new plugins and everything is again working fine.
So far so good to solve the problem. Another way to solve that issue could be, to update to the latest Sitecore CLI version, remove the sitecore.json (If the file is already present in the solution, the following init command, would simply ignore this) file and use the dotnet sitecore init command to initialize everything again. In this case the sitecore.json would be generated with exactly these two plugins already installed.
- migrated