hubspot-api-python 11.0.0 breaks environments using urllib3 2.x

What happened

After upgrading hubspot-api-python to 11.0.0, pip now refuses to resolve my environment because the SDK dropped support for urllib3 2.x. I have already adopted urllib3 2.x and the 11.0.0 release notes do not even mention the removal. Is this intentional, and how do I keep using urllib3 2.x with the HubSpot client?

The fix that worked

It was not intentional. The 11.0.0 release removed urllib3 2.x compatibility in a changeset that slipped in without a release-notes callout. The maintainers fixed it right away: 11.1.0 restores urllib3 2.x compatibility, and users confirmed that with 11.1.0 they could install urllib3 v2.x alongside the HubSpot client with no dependency conflict. So just upgrade to 11.1.0 or newer. One extra detail from the thread: 11.0.0 also added requests as a dependency (so the SDK can be exercised via curl for debugging), which was a separate deliberate change.

In the thread hubspot-api-python 11.0.0 breaks environments using urllib3 2.x, the question was: After upgrading hubspot-api-python to 11.0.0, pip now refuses to resolve my environment because the SDK dropped support for urllib3 2.x. I have already adopted urllib3 2.x and the 11.0.0 release notes do not even mention the removal. Is this intentional, and how do I keep using urllib3 2.x with the HubSpot client? The verified resolution: It was not intentional. The 11.0.0 release removed urllib3 2.x compatibility in a changeset that slipped in without a release-notes callout. The maintainers fixed it right away: 11.1.0 restores urllib3 2.x compatibility, and users confirmed that with 11.1.0 they could install urllib3 v2.x alongside the HubSpot client with no dependency conflict. So just upgrade to 11.1.0 or newer. One extra detail from the thread: 11.0.0 also added requests as a dependency (so the SDK can be exercised via curl for debugging), which was a separate deliberate change. Original discussion: https://vectle.com/threads/thr_I8ZAdUqZO-jvn0wvqnjYyQ