---
title: "What's new in Content SDK 2.2"
slug: "what-s-new-in-content-sdk-2-2"
abstract: "Learn about the new improvements and features in Content SDK 2.2 and how to update your existing application to take advantage of them."
---
# What's new in Content SDK 2.2

Content SDK 2.2 introduces on-demand static revalidation (OSR), draft component workflows, developer experience improvements, and several important bug fixes and maintenance updates.

To update your existing Content SDK 2.1 application to 2.2:

1. In your existing application's `package.json` file, update the following packages to version `2.2.0`.

    ```json
    "@sitecore-content-sdk/cli": "^2.2.0",
    "@sitecore-content-sdk/nextjs ": "^2.2.0",
    ```

    > [!note]
    > The Content SDK has transitioned to independent versioning for its packages. Due to this, all packages won't be updated to the latest version.

2. Install the dependencies with the following command:

    ```shell
    npm install
    ```

## Notable improvements and bug fixes

The following features, improvements, and bug fixes have been introduced in Content SDK 2.2. This is not an exhaustive list. Please review the [Content SDK release page](https://github.com/Sitecore/content-sdk/releases) for a complete list of all changes for version 2.2.

### On-demand static revalidation

See [On-demand static revalidation for App Router apps](https://doc.sitecore.com/sai/en/developers/content-sdk/20/on-demand-static-revalidation-for-app-router-apps.html "On-demand static revalidation for App Router apps") for more information.

### Support for draft components

Content SDK 2.2 introduces support for draft components in the Design Studio. Before this, the Design Studio required a `renderingId`, exposed as `sc_renderingId` in query parameters, whenever rendering a component in isolation. This restriction prevented components that had not yet been fully registered in Sitecore, or draft components, from being previewed in the Design Studio.

This change makes the `sc_renderingId` optional, enabling the Design Studio to render draft or unregistered components without a rendering ID being present.

### New proxy execution context

See [Using the proxy execution context](https://doc.sitecore.com/sai/en/developers/content-sdk/20/using-the-proxy-execution-context.html "Using the proxy execution context") for more information.