[Snyk] Security upgrade aiohttp from 3.8.1 to 3.13.4

[Robthreefold]

Snyk has created this PR to fix 10 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• rm-empty-targets/requirements.txt

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Information Exposure

[Robthreefold]

This upgrade of aiohttp from 3.8.1 to 3.13.4 introduces significant breaking changes, most notably in the application shutdown process starting from version 3.10.0.

Key Breaking Changes:

• Graceful Shutdown Logic (v3.10.0): The application shutdown logic has been changed to only wait for request handlers, and no longer waits for all background tasks to complete. Applications that rely on the old behavior for background task completion during shutdown may break or leak resources.
• Python Version Support: Support for Python 3.6 was dropped in version 3.9.0. Environments using this older Python version must be upgraded.
• Cookie Storage (v3.10.0): The internal storage format for CookieJar has changed. Cookies saved with older versions may not be loadable without migration. The changelog provides a migration script for this purpose.
• Decompression Limit (v3.13.3): To address security concerns (decompression bombs), a default maximum output size of 32MiB is now enforced per decompression call. This could affect applications that handle larger compressed payloads.

Recommendation:

Developers must review their application's background task management and graceful shutdown implementation. It is highly recommended to use a library like aiojobs to manage the lifecycle of background tasks to ensure they are handled correctly during shutdown, as suggested by the aiohttp documentation.

Source: Official Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[Robthreefold]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.