-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Bump aiohttp
to 3.11.1
#44036
Bump aiohttp
to 3.11.1
#44036
Conversation
pnuckowski/aioresponses#262 hasn't been merged yet though |
It's unllikely to be merged - the maintainer seems to be MIA for 2 years. That's why likely aiohttp brought back compatiblity with released version of the aioresponses as it is popular |
looks good. Maybe one nit - would be great to add comment with link to the issue in provider.yaml |
(we have it in commit so no strictly necessary - but it safes git blame etc.) |
Done |
Bump `aiohttp` to `3.11.1` aio-libs/aiohttp#9866 was fixed by pnuckowski/aioresponses#262 (comment) https://pypi.org/project/aiohttp/3.11.1/
Damn! last commit msg was used as commit title :( |
Good we have the comment :) |
aio-libs/aiohttp#9866 was fixed by pnuckowski/aioresponses#262 (comment)
https://pypi.org/project/aiohttp/3.11.1/
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.