chore(deps): bump the poetry group across 1 directory with 162 updates

[dependabot]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

---

Important

Bump dependencies across pyproject.toml, requirements-examples.txt, and requirements.txt to ensure compatibility and security.

• Dependencies:
  • Bump jiter to <0.12 in pyproject.toml.
  • Update pytest-asyncio to >=0.24.0,<2.0.0 in pyproject.toml.
  • Bump mkdocstrings to <0.31.0 in pyproject.toml.
  • Update fastapi to <0.121.0 and redis to <8.0.0 in pyproject.toml.
  • Bump anthropic to ==0.71.0 and groq to <0.34.0 in pyproject.toml.
  • Update perplexity to <3.0.0 in pyproject.toml.
  • Bump datasets to <5.0.0 in pyproject.toml.
  • Update ruff to ==0.14.2, pre-commit to ==4.3.0, and pyright to ==1.1.406 in requirements-examples.txt.
  • Update multiple dependencies in requirements.txt, including aiohttp, boto3, fastapi, google-cloud-aiplatform, openai, and many others.

^{This description was created by for 40c0b47. You can customize this summary. It will automatically update as commits are pushed.}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	instructor	4424366	Oct 27 2025, 09:42 PM

[ellipsis-dev]

Caution

Changes requested ❌

Reviewed everything up to 40c0b47 in 2 minutes and 22 seconds. Click for details.

• Reviewed 481 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 2 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. requirements.txt:73

• Draft comment:
  Groq version conflict: 'groq==0.33.0' does not meet the constraint 'groq>=0.4.2,<0.34.0' in pyproject.toml.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 85% The comment is pointing out a real version conflict. The requirements.txt specifies version 0.33.0 which is less than the minimum 0.4.2 required in pyproject.toml. This could cause dependency issues. The comment provides a clear fix by suggesting to use the constraint from pyproject.toml. The comment assumes that pyproject.toml is the source of truth, but maybe requirements.txt has a good reason for using an older version. Also, this is a dependency version change which our rules say we should ignore. While we generally ignore dependency changes, a direct version conflict between project files is a more serious issue that could break the build. This isn't just about updating a version, but fixing an inconsistency. Despite our general rule about ignoring dependency changes, this comment identifies a clear version conflict that needs to be resolved, so we should keep it.

2. requirements.txt:67

• Draft comment:
  google-genai version conflict: 'google-genai==1.46.0' is below the required '>=1.5.0' as specified in pyproject.toml.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

Workflow ID: wflow_M3jTFocauWNTQQsT

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

OpenAI version conflict: 'openai==2.6.0' violates the constraint 'openai<2.0.0,>=1.70.0' from pyproject.toml.

Suggested change

	openai==2.6.0
	openai==1.99.0