fix: update openai dependency version constraints in pyproject.toml and uv.lock to support v2

[vishnu-itachi]

Important

Update openai dependency version constraints in pyproject.toml and uv.lock to support version 2.

• Dependencies:
  • Update openai version constraint in pyproject.toml to >=2.0.0,<3.0.0.
  • Update openai version constraint for perplexity extra in pyproject.toml to >=2.0.0,<3.0.0.
• Lock File:
  • Update openai version in uv.lock to 2.6.0.
  • Update sdist and wheels URLs and hashes in uv.lock for openai version 2.6.0.
  • Increment revision in uv.lock from 2 to 3.

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 81a141c in 1 minute and 27 seconds. Click for details.

• Reviewed 65 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 8 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. pyproject.toml:7

• Draft comment:
  Updated openai dependency version constraint to v2. Ensure downstream code handles any breaking API changes.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 85% This comment is about a dependency change, specifically updating the openai dependency version. The comment suggests ensuring downstream code handles any breaking API changes, which falls under the rule of not commenting on dependency changes or asking the author to ensure compatibility. Therefore, this comment should be removed.

2. pyproject.toml:100

• Draft comment:
  Ensure the perplexity extra now consistently uses openai v2 constraints.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

3. uv.lock:2

• Draft comment:
  Lockfile revision bump from 2 to 3 reflects dependency updates; ensure all environments are updated accordingly.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 85% This comment is purely informative and does not provide a specific suggestion or request for action. It violates the rule against making purely informative comments.

4. uv.lock:1905

• Draft comment:
  Align openai requires-dist specifier with project requirements for v2.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 85% This comment is related to aligning the requires-dist specifier with project requirements. It seems to be about dependencies, which is not allowed to be commented on according to the rules. Therefore, this comment should be removed.

5. uv.lock:1906

• Draft comment:
  Ensure extra 'perplexity' dependency for openai is updated to v2 constraints.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 60% <= threshold 85% This comment is about a dependency change, specifically asking to ensure that a dependency is updated to a specific version. The rules state not to comment on pure dependency changes or library versions that are not recognized. However, this comment is specific about a version constraint, which might be relevant if it affects functionality or compatibility. Since it doesn't ask for confirmation or testing, it might be useful if the version constraint is important for the code to function correctly.

6. uv.lock:3290

• Draft comment:
  Openai package version updated to 2.6.0. Confirm that internal code and integrations are compatible with v2 changes.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 85% This comment is asking the PR author to confirm compatibility with a new version of a package, which falls under the rule of not commenting on dependency changes or asking for confirmation of intentions. Therefore, it should be removed.

7. uv.lock:3301

• Draft comment:
  Verify that the new sdist URL, hash, and metadata for openai v2.6.0 are correct and secure.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 85% This comment is asking the PR author to verify the correctness and security of the new sdist URL, hash, and metadata for a specific version of a library. This falls under the rule of not asking the PR author to double-check things or ensure correctness, which is not allowed.

8. uv.lock:3306

• Draft comment:
  Check that the updated wheel URL, hash, and size for openai v2.6.0 meet distribution standards.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 85% This comment is related to dependency changes, specifically the URL, hash, and size of a library version. According to the rules, I should not comment on pure dependency changes or library versions that I don't recognize. Therefore, this comment should be removed.

Workflow ID: wflow_7JVAaHHwjUuURLu7

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