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

update litellm #1747

Merged
merged 2 commits into from
Feb 7, 2025
Merged

update litellm #1747

merged 2 commits into from
Feb 7, 2025

Conversation

wintonzheng
Copy link
Contributor

@wintonzheng wintonzheng commented Feb 7, 2025

Important

Update litellm dependency from version 1.60.0 to 1.60.6 in pyproject.toml.

  • Dependencies:
    • Update litellm version from 1.60.0 to 1.60.6 in pyproject.toml.

This description was created by Ellipsis for 6e64746. It will automatically update as commits are pushed.

<!-- ELLIPSIS_HIDDEN -->

> [!IMPORTANT]
> Update `litellm` version from `1.60.0` to `1.60.6` in `pyproject.toml`.
>
>   - **Dependencies**:
>     - Update `litellm` version from `1.60.0` to `1.60.6` in `pyproject.toml`.
>
> <sup>This description was created by </sup>[<img alt="Ellipsis" src="https://img.shields.io/badge/Ellipsis-blue?color=175173">](https://www.ellipsis.dev?ref=Skyvern-AI%2Fskyvern-cloud&utm_source=github&utm_medium=referral)<sup> for 09e9ec8997184e7f123c94c9b88aa02211ec3a14. It will automatically update as commits are pushed.</sup>

<!-- ELLIPSIS_HIDDEN -->
<!-- ELLIPSIS_HIDDEN -->

> [!IMPORTANT]
> Update `litellm` version from `1.60.0` to `1.60.6` in `pyproject.toml`.
>
>   - **Dependencies**:
>     - Update `litellm` version from `1.60.0` to `1.60.6` in `pyproject.toml`.
>
> <sup>This description was created by </sup>[<img alt="Ellipsis" src="https://img.shields.io/badge/Ellipsis-blue?color=175173">](https://www.ellipsis.dev?ref=Skyvern-AI%2Fskyvern-cloud&utm_source=github&utm_medium=referral)<sup> for 09e9ec8997184e7f123c94c9b88aa02211ec3a14. It will automatically update as commits are pushed.</sup>

<!-- ELLIPSIS_HIDDEN -->
Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Skipped PR review on 6e64746 because no changed files had a supported extension. If you think this was in error, please contact us and we'll fix it right away.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me! Reviewed everything up to 6e64746 in 21 seconds

More details
  • Looked at 13 lines of code in 1 files
  • Skipped 1 files when reviewing.
  • Skipped posting 2 drafted comments based on config settings.
1. pyproject.toml:19
  • Draft comment:
    Update litellm dependency version to 1.60.6. Verify compatibility with existing code.
  • Reason this comment was not posted:
    Confidence changes required: 50% <= threshold 50%
    None
2. pyproject.toml:19
  • Draft comment:
    Bump litellm from 1.60.0 to 1.60.6. Ensure this patch upgrade is compatible with your usage. Consider using caret (e.g. '^1.60.6') if semver guarantees allow for flexible updates.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
    The comment is about a dependency version bump, which is generally not something to comment on unless there's a specific issue with the version change. The suggestion to ensure compatibility and consider using caret for flexible updates is not specific enough to be useful. It violates the rule against commenting on dependency changes without specific issues.

Workflow ID: wflow_wNetuRnrQZOJtwln


You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

@LawyZheng LawyZheng merged commit da6fb39 into main Feb 7, 2025
7 checks passed
@LawyZheng LawyZheng deleted the lawy/upgrade-litellm branch February 7, 2025 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants