chore: regenerate poetry.lock to unblock CI (pyproject.toml content hash drift) - #24082
Merged
1 commit merged intoMar 19, 2026
Merged
Conversation
Contributor
|
No reviewable files after applying ignore patterns. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
This was referenced Mar 19, 2026
fzowl
pushed a commit
to fzowl/litellm
that referenced
this pull request
Jun 24, 2026
This pull request was closed.
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.
Summary
pyproject.tomlcontent hash changed butpoetry.lockwas not updated, causing all PR builds to fail atpoetry installwith Poetry 2.3.2poetry.lock(thecontent-hashfield)Impact
Every open PR is failing CI at the dependency install step — no tests are running. This unblocks all of them.
Test plan
poetry installstep on this PR