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

deps: Update dependency aiohttp to v3.9.1 #916

Merged

Conversation

renovate-bot
Copy link
Contributor

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
aiohttp ==3.9.0 -> ==3.9.1 age adoption passing confidence

Release Notes

aio-libs/aiohttp (aiohttp)

v3.9.1: 3.9.1

Compare Source

Bugfixes

  • Fixed importing aiohttp under PyPy on Windows.

    (#​7848)

  • Fixed async concurrency safety in websocket compressor.

    (#​7865)

  • Fixed ClientResponse.close() releasing the connection instead of closing.

    (#​7869)

  • Fixed a regression where connection may get closed during upgrade. -- by :user:Dreamsorcerer

    (#​7879)

  • Fixed messages being reported as upgraded without an Upgrade header in Python parser. -- by :user:Dreamsorcerer

    (#​7895)



Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@jackwotherspoon jackwotherspoon merged commit b6f9485 into GoogleCloudPlatform:main Nov 27, 2023
13 checks passed
@renovate-bot renovate-bot deleted the renovate/aiohttp-3.x branch November 27, 2023 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants