Fix aiohttp dependency conflict by upgrading aiosignal to 1.4.0 #21
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.
This PR resolves the workflow failures that were occurring when Dependabot attempted to upgrade aiohttp from 3.10.11 to 3.12.14 in PR #19.
Problem
The Dependabot PR was failing because it only upgraded aiohttp but didn't update the dependent package aiosignal. According to the aiohttp 3.12.14 changelog, this version requires aiosignal>=1.4.0 to resolve typing issues:
However, the requirements.txt file still had
aiosignal==1.3.1, creating a dependency conflict that caused installation failures in CI workflows.Solution
Updated
src/requirements.txtto upgrade both packages to compatible versions:Testing
This minimal change ensures that when dependencies are installed fresh (as in CI workflows), there won't be version conflicts between aiohttp 3.12.14 and aiosignal 1.3.1.
Fixes #20.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.