@nateprewitt Did we want to change the version ranges allowed for urllib3 to allow 2.0.0 without a warning? I figure this is safe now that urllib3 integration test suite passes w/ requests without any patches.

Ideally, I think we would leave the pin in place to minimize blast radius. We shouldn't break now that the chunking is merged if users are forcibly upgrading outside the supported range. After we get some prime time with the major version bump, I'm fine cutting another minor version to expand support. I just don't want to opt people into a major version bump without warning.

Thank you!