[SKY-8441] Remove python-ecdsa from integration lock files#5190
Merged
[SKY-8441] Remove python-ecdsa from integration lock files#5190
Conversation
AronPerez
commented
Mar 22, 2026
Comment on lines
+47
to
49
|
|
||
| [tool.hatch.build.targets.sdist] | ||
| include = ["skyvern_llamaindex"] |
Contributor
Author
There was a problem hiding this comment.
Resolve skyvern from the local workspace so the lock file picks up the python-jose → PyJWT migration instead of the stale PyPI metadata
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the LangChain and LlamaIndex integration environments to resolve skyvern from the local workspace (instead of PyPI) so their lockfiles pick up the previously-remediated JWT dependency change and drop the python-jose → ecdsa chain.
Changes:
- Add
[tool.uv.sources]entries so integrations resolveskyvernfrom../..(repo root). - Regenerate
uv.lockfiles to removepython-jose/ecdsa(and related packages likersa) from the dependency graph. - Update locked
skyvernsource in the integration lockfiles to a local directory reference.
Reviewed changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| integrations/llama_index/pyproject.toml | Points skyvern dependency resolution at the local repo via [tool.uv.sources]. |
| integrations/llama_index/uv.lock | Re-locks dependencies using local skyvern, removing python-jose/ecdsa and updating the resolved tree. |
| integrations/langchain/pyproject.toml | Points skyvern dependency resolution at the local repo via [tool.uv.sources]. |
| integrations/langchain/uv.lock | Re-locks dependencies using local skyvern, removing python-jose/ecdsa and updating the resolved tree. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
wintonzheng
approved these changes
Mar 22, 2026
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.
Summary
[tool.uv.sources]tointegrations/llama_index/andintegrations/langchain/to resolve skyvern from local workspace instead of PyPIpython-ecdsaandpython-josefrom the dependency treeContext
PR #5184 replaced
python-josewithPyJWTin the main project, but the integration lock files still resolvedskyvern==1.0.24from PyPI (which still declarespython-jose). This change points the integrations at the local source so the lock files pick up the fix.Test Plan
grep -r "ecdsa" integrations/returns no resultsgrep -r "python-jose" integrations/returns no resultsuv lockresolves successfully for both integrations