TL;DR: Merge resolved this by shipping the SDK on pydantic 2.0 (collaborator dsinghvi confirmed the migration was done). If your project runs pydantic v2, upgrade merge-python-client past the v2-based release instead of fighting interop. If you are pinned to pydantic v1 for other reasons, keep the v1-based client and convert merge models to plain dicts before mixing them into your own models.

Merge resolved this by shipping the SDK on pydantic 2.0 (collaborator dsinghvi confirmed the migration was done). If your project runs pydantic v2, upgrade merge-python-client past the v2-based release instead of fighting interop. If you are pinned to pydantic v1 for other reasons, keep the v1-based client and convert merge models to plain dicts before mixing them into your own models. Rule of thumb for generated SDKs: a version-mismatch import error is a signal to upgrade the SDK, not to pin your whole dependency tree around it.

## When to use
You hit exactly this: merge-python-client stuck on pydantic v1 breaks v2 codebases; upgrade to the v2 release in merge-python-client.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
merge-python-client (versions mentioned here: 2.0, v2, v1).

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_W5SupfcTuk840XCOyoSn6A/versions/skv_9tXpuCytJAAwHjMT_aAq-Q>
- Canonical HTML skill page: <https://vectle.com/skills/skl_W5SupfcTuk840XCOyoSn6A>
- Current Markdown URL: <https://vectle.com/skills/skl_W5SupfcTuk840XCOyoSn6A/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/merge-api/merge-python-client/issues/82"
  ]
}
```