Repository navigation
[WIP] Dependency sweep: no changes yet, lock not resolved - #2623
Draft
Derek Worthen (dworthen) with Copilot wants to merge 3 commits into
Draft
Derek Worthen (dworthen) with Copilot wants to merge 3 commits into
Derek Worthen (dworthen) with Copilot wants to merge 3 commits into
Conversation
Co-authored-by: dworthen <624870+dworthen@users.noreply.github.com>
Co-authored-by: dworthen <624870+dworthen@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update dependencies to latest versions
[WIP] Dependency sweep: no changes yet, lock not resolved
Nov 9, 2026
This branch has not been deployed
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.
Description
This is the automated dependency sweep. The PR makes no net changes yet. The bumped specifiers were committed and then reverted because
uv lock --upgradenever resolved through the Microsoft feed proxy, and leaving them in would leavepyproject.tomlout of sync withuv.lock.Related Issues
Automated "Update Dependencies Sweep" issue.
Proposed Changes
Nothing has landed yet. These are the planned bumps, each the newest release more than 7 days old on PyPI:
devgroup: coverage 7.17, ipykernel 7.4, mkdocs-material 9.8, mkdocs-jupyter 0.27, pandas-stubs 3.1, poethepoet 0.49, pytest 9.2, ruff 0.17packages/*: pydantic 2.14, azure-identity 1.27, azure-cosmos 4.17, azure-storage-blob 12.31, pandas 3.1, pyarrow 26, lancedb 0.41, devtools 0.13, json-repair 0.64, markitdown 0.1.9, litellm==1.106.6, fastapi>=0.162.0, orjson>=3.13.0~=2.4and networkx~=3.6: newer versions require Python 3.12+.~=3.9.0: 3.10 breaks the noun-phrase extraction golden data.<1.3: 1.3 breaks the Leiden clustering golden data.Checklist
poe checkandpoe test_unitpassed before any change; nothing was tested after the bumps.)Additional Notes
Two problems with the feed proxy blocked the lock:
.whl.metadatareturns 404 until then (seen with spacy 3.8.17/3.8.18, thinc 8.3.14 and preshed 3.0.15). Retrying moves past one wheel at a time, but the lock never finished in the time available.--exclude-newerfilters on the date the proxy fetched each wheel, which can be days after the PyPI release. litellm 1.106.6 (PyPI 10-28, proxy 11-04), pandas-stubs 3.1 (PyPI 10-29, proxy 11-05) and pytest 9.2 (proxy 11-03) were rejected even though PyPI released them more than 7 days ago.To finish:
After that: fix any breakage from the upgrades, add a semversioner
patchentry, and re-runpoe checkandpoe test_unit. Likely breakage includes new ruff 0.17 rules, and litellm ≥1.106 may needtyping.castaround itscompletion()/embedding()calls in graphrag-llm.