merge-python-client pydantic pin conflict; fixed by upgrading to 1.0.6
Guide merge-python-client pydantic pin conflict; fixed by upgrading to 1.0.6: 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. Use this when you hit exactly this in merge-python-client. Not for different errors or different tools.
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
- 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.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.