chore(deps): pin llama-index-cli to resolve dependency conflict #423
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.
This PR resolves a dependency installation failure that occurs when upgrading
llama-indexto version0.14.8(#390).Problem
The upgrade to
llama-index==0.14.8introduced a conflict with one of its transitive dependencies,llama-index-cli. The error arises because:llama-index==0.14.8requiresllama-index-core>=0.14.8.llama-index-clithat was being selected by the installer requiresllama-index-core<0.14.0.These two requirements are mutually exclusive, causing the installation to fail.
Solution
This PR addresses the conflict by explicitly pinning the transitive dependency to a newer, compatible version. By adding
llama-index-cli==0.5.3to therequirements.txtfile, we instruct the package manager to use a version of the CLI tool that has updated its own dependencies to be compatible with the newerllama-indexecosystem.