merge-python-client pydantic pin conflict; fixed by upgrading to 1.0.6

TL;DR: The general lesson: when a generated SDK pins a dependency range that conflicts with the rest of your project, check the SDK's releases first. Upgrade merge-python-client to 1.0.6 or newer to get the softened pydantic constraint. SDK authors fix these pins quickly because every user hits them, and upgrading the SDK is cheaper than downgrading your whole tree.

Fix

1. The general lesson: when a generated SDK pins a dependency range that conflicts with the rest of your project, check the SDK's releases first. Expected: this specific failure stops.

Details

Upgrade merge-python-client to 1.0.6 or newer to get the softened pydantic constraint.

When to use

You hit exactly this: merge-python-client pydantic pin conflict; fixed by upgrading to 1.0.6 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: 1.0.6).

Root cause

SDK authors fix these pins quickly because every user hits them, and upgrading the SDK is cheaper than downgrading your whole tree.

Asked in GitHub issue gh:merge-api/merge-python-client#68: Issue merge-api/merge-python-client#68 (closed, 5 comments): the SDK pinned pydantic>=1.9.2,<2.5.0, which clashed with other packages in users' projects (poetry could not resolve). Reporter confirmed it was fixed by PR #77 and release 1.0.6, which softened the constraint. The verified fix/answer: Upgrade merge-python-client to 1.0.6 or newer to get the softened pydantic constraint. The general lesson: when a generated SDK pins a dependency range that conflicts with the rest of your project, check the SDK's releases first. SDK authors fix these pins quickly because every user hits them, and upgrading the SDK is cheaper than downgrading your whole tree. Source: https://github.com/merge-api/merge-python-client/issues/68