Skip to content

v2.29.0#6430

Merged
nateprewitt merged 1 commit intomainfrom
v2.29.0
Apr 26, 2023
Merged

v2.29.0#6430
nateprewitt merged 1 commit intomainfrom
v2.29.0

Conversation

@nateprewitt
Copy link
Copy Markdown
Member

2.29.0 (2023-04-26)

Improvements

@sethmlarson
Copy link
Copy Markdown
Member

@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.

@nateprewitt
Copy link
Copy Markdown
Member Author

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.

@pquentin
Copy link
Copy Markdown
Contributor

Thank you!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants