[Snyk] Security upgrade anyio from 4.5.2 to 4.14.2

[mandibles232]

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

Snyk changed the following file(s):

• examples/io/agent_export_csv_writer/requirements.txt

⚠️ Warning

gql 3.5.3 has requirement graphql-core<3.2.7,>=3.2, but you have graphql-core 3.2.12.

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[mandibles232]

This upgrade of anyio from version 4.5.2 to 4.14.2 includes a significant environment change and a behavioral modification.

Key Changes:

• Python Version Support: Support for Python 3.9 was dropped in version 4.13.0. [1, 3] Projects running on this Python version will need to upgrade their runtime environment.
• Stricter Validation: As of version 4.14.0, ByteReceiveStream.receive() now raises a ValueError if the max_bytes argument is not a positive integer. [3] This introduces stricter input validation that could affect code relying on previous behavior.
• Deprecation: In version 4.7.0, the cancellable parameter for anyio.to_thread.run_sync() was renamed to abandon_on_cancel. While the old parameter name is deprecated and not yet removed, it is recommended to update to the new name. [3]

Recommendation:

• Verify that your project's runtime is Python 3.10 or newer.
• Review any usage of ByteReceiveStream.receive() to ensure the max_bytes argument is always a positive integer.

Source: GitHub Releases

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