> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cookiechimp.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Versions and deployment

> Package versions, connected deployment and optional integrations.

SDK **1.2.0** is published on npm. All nine packages use the same version and
include verified provenance from the CookieChimp GitHub release workflow. See
[the release notes](https://github.com/cookiechimp/cookiechimp-sdk/releases/tag/v1.2.0).

For a React application:

```sh theme={null}
npm install @cookiechimp/core@1.2.0 @cookiechimp/react@1.2.0
```

For Next.js, also install the server integration:

```sh theme={null}
npm install @cookiechimp/nextjs@1.2.0
```

For React Native or Expo:

```sh theme={null}
npm install @cookiechimp/react-native@1.2.0 @react-native-async-storage/async-storage
```

Follow the [React Native guide](https://docs.cookiechimp.com/docs/sdk/react-native.md) for connected
configuration, native preferences and control of analytics or advertising SDKs.

Keep the CookieChimp packages you use on matching versions. SDK 1.2.0 adds React
Native support, tracking-image blocking, smaller connected sync and additional
US state privacy formats. It includes the platform JSON banner, category/vendor
preferences and consent UI locale isolation introduced in 1.1.0.
The `@cookiechimp/react/platform` and `@cookiechimp/react/platform.css` entries
require 1.1.0 or newer. The 1.0.0 package cohort supports the standard consent
integrations.

## Documentation

The Consent SDK guides live with the existing CookieChimp documentation on
Mintlify. The SDK repository keeps the source guides and runnable examples;
Mintlify provides navigation, search, Markdown views and AI documentation indexes.

## Connected mode

Local mode needs no account. Connected mode requires the shared platform config
and consent-ingestion endpoints to be deployed and tested with the project's
account. Cached or in-code config is a fallback; it does not prove consent records
were delivered. Verify connected delivery before using it in production.

## Optional IAB integrations

Production TCF requires a valid registered CMP ID, a current vendor list and IAB
validation. Applications supply the GVL and the authoritative feature decision.
The SDK does not provide a GVL CDN or enforce connected Pro entitlements.
See the [reference](https://docs.cookiechimp.com/docs/sdk/reference.md) for GPP coverage and TCF limitations.

## Translations

Banner and TCF interface labels are available in 33 editorially reviewed locales,
including right-to-left Arabic and Hebrew. See [translations](https://docs.cookiechimp.com/docs/sdk/translations.md).

## Upgrading

Update the CookieChimp packages together and check the package changelogs for
changes affecting your integration. Verify saved choices, your banner settings
and connected consent delivery in your application after an upgrade.