Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v2.29.0 #6430

Merged
merged 1 commit into from Apr 26, 2023
Merged

v2.29.0 #6430

merged 1 commit into from Apr 26, 2023

Conversation

nateprewitt
Copy link
Member

2.29.0 (2023-04-26)

Improvements

@sethmlarson
Copy link
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
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
Contributor

Thank you!

@nateprewitt nateprewitt merged commit 87d63de into main Apr 26, 2023
36 checks passed
@nateprewitt nateprewitt deleted the v2.29.0 branch April 26, 2023 15:19
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 27, 2024
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.

None yet

4 participants