> **Can't find what you're looking for?** Use `search_docs` on the docs MCP server at `https://ensforge.com/api/mcp` to find what you need.

# Upgrade to 0.2

Version 0.2.0 reduces the root type surface and separates optional Wagmi integration. It also aligns
the Sepolia contract exports with the deployed July snapshot. If you use React 0.1.0, apply the
[0.1.1 changes](/migrations/0-1-1) as well.

## Moved action-specific type exports

Import SDK action types from their action group instead of the package root:

```ts
import type { GetOwnerParameters } from "@ensforge/sdk"; // [!code --]
import type { GetOwnerParameters } from "@ensforge/sdk/name"; // [!code ++]
```

Apply the same pattern to other groups, such as `@ensforge/sdk/records` and
`@ensforge/sdk/registration`. Core also exposes group entrypoints such as `@ensforge/core/name`.
Keep the SDK constructor imported from `@ensforge/sdk`; the grouped type imports do not create
separate SDK instances.

## Moved Wagmi integration to dedicated entrypoints

Viem-only applications no longer need to install Wagmi. Applications that configure ensforge through
Wagmi should use its explicit entrypoints:

:::code-group
```ts [SDK]
import { createEnsforge } from "@ensforge/sdk/wagmi";
```

```ts [Core]
import { createWagmiConfig } from "@ensforge/core/wagmi";
```
:::

See [SDK getting started](/sdk/getting-started) or
[createWagmiConfig](/core/api/create-wagmi-config) for the configuration shape.

## Removed undeployed contract exports

The contract package removes forward-looking interfaces and the `ethRegistrarV2InterfaceRenewBatchAbi`
and `ethRenewerV2InterfaceRenewBatchAbi` fragments, which described batch methods that were not deployed.
If you imported those exports or encoded contract calls yourself, update to the ABIs and interfaces
shipped with your target deployment. For SDK renewals, use
[renewNames](/sdk/api/registration/renew-names) instead of depending on a removed contract helper.

Do not mix newer contract addresses with older ABIs. If upgrading directly to the current release,
use the [0.6 Sepolia profile](/migrations/0-6), not the historical July deployment.

## Preserve submitted write progress

Sequential write plans retain submitted transaction hashes when confirmation fails. Resume the
saved plan rather than starting the same write again. A confirmation error does not necessarily
mean the transaction was never submitted.