⬆️(deps): Update langchain-litellm requirement from <0.7.0,>=0.4.0 to >=0.6.4,<0.7.0 in /packages/meeseeks_core#121
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Updates the requirements on [langchain-litellm](https://github.com/langchain-ai/langchain-litellm) to permit the latest version. - [Release notes](https://github.com/langchain-ai/langchain-litellm/releases) - [Changelog](https://github.com/langchain-ai/langchain-litellm/blob/main/CHANGELOG.md) - [Commits](langchain-ai/langchain-litellm@langchain-litellm==0.6.2...langchain-litellm==0.6.4) --- updated-dependencies: - dependency-name: langchain-litellm dependency-version: 0.6.4 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| "langchain-core>=1.2.8,<2.0.0", | ||
| "langchain-community>=0.4.1,<0.5.0", | ||
| "langchain-litellm>=0.4.0,<0.7.0", | ||
| "langchain-litellm>=0.6.4,<0.7.0", |
There was a problem hiding this comment.
🟡 uv.lock not updated: locked version 0.4.0 violates new >=0.6.4 constraint
The pyproject.toml now requires langchain-litellm>=0.6.4,<0.7.0, but uv.lock was not regenerated. The lock file still records the old specifier >=0.4.0,<0.7.0 at uv.lock:1983 and pins version 0.4.0 at uv.lock:1479, which does not satisfy the new >=0.6.4 lower bound. Running uv sync will detect the mismatch and need to re-resolve, meaning the committed lock file is stale and doesn't reflect the intended dependency change.
Prompt for agents
The uv.lock file needs to be regenerated to match the updated pyproject.toml constraint. Run `uv lock` (or `uv sync`) from the repo root to update the lock file so that langchain-litellm resolves to a version >= 0.6.4. The current lock file at uv.lock:1479 pins version 0.4.0 and at uv.lock:1983 records the old specifier >=0.4.0,<0.7.0, both of which are now stale.
Was this helpful? React with 👍 or 👎 to provide feedback.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the requirements on langchain-litellm to permit the latest version.
Release notes
Sourced from langchain-litellm's releases.
Changelog
Sourced from langchain-litellm's changelog.
Commits
28851fcfix: bump pyproject.toml to 0.6.4 and harden release pipeline (#127)0685d2arelease(litellm): 0.6.4 (#113)8912d08fix: downgradetool_choiceto auto when thinking is enabled on Claude (#126)6cb409dbuild(deps): bump aiohttp from 3.13.3 to 3.13.4 in the uv group across 1 dire...06c893dfix: filtertool_usecontent blocks from AI message dicts (#125)df1216cfix: populatemodel_nameinresponse_metadatafor streaming and router pa...e2515bdchore: fix integration tests (#123)6177e47chore: rename tests (#122)ae18705fix: extract reasoning tokens and handle pydantic usage in metadata (#121)085737achore: format (#120)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)