🔧 chore(deps): regenerate stale uv.lock (langchain-core constraint)#300
Merged
Conversation
uv.lock was out of sync with pyproject.toml's langchain-test group (langchain-core specifier <1.5.0 in the lock vs <1.6.0 in pyproject.toml, left behind by #296's constraint bump). This was failing every PR's CI with `uv sync --locked` erroring "lockfile needs to be updated" — including dependency-upgrade PRs that don't touch pyproject.toml/uv.lock at all (e.g. #297, actions/setup-uv). Verified: unit (1131 passed) and integration (38 passed) suites both green with the regenerated lock.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
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
1 participant
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.
uv.lockwas out of sync withpyproject.toml'slangchain-testgroup (langchain-corespecifier<1.5.0in the lock vs<1.6.0in pyproject.toml, left behind by #296's constraint bump). This was failing every PR's CI withuv sync --lockederroring "lockfile needs to be updated" — including dependency-upgrade PRs that don't touchpyproject.toml/uv.lockat all (e.g. #297, actions/setup-uv).Verified locally: unit (1131 passed) and integration (38 passed) suites both green with the regenerated lock.