Upgrade requests and aiohttp to fix SSL handling and header parsing issues #87
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RinZ27
changed the title
RinZ27
force-pushed
the
fix/upgrade-critical-deps
branch
6 times, most recently
from
c7c6566 to
4f194a4
Compare
RinZ27
force-pushed
the
fix/upgrade-critical-deps
branch
from
eb0c1a3 to
9c7dec9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumped
requestsandaiohttpto their latest stable versions.Previous constraints were pulling in
urllib3< 2.3.0 andaiohttp< 3.10, which have known quirks with SSL/TLS connection handling and header parsing. After reviewing the logic, I decided that ensuring the SDK remains robust when dealing with API calls and image downloads should be a priority.Also regenerated
uv.lockto reflect these dependency updates.