Repository navigation
Conversation
Updates the requirements on [uvicorn](https://github.com/Kludex/uvicorn), [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy), [greenlet](https://github.com/python-greenlet/greenlet), [anthropic](https://github.com/anthropics/anthropic-sdk-python), [boto3](https://github.com/boto/boto3), [networkx](https://github.com/networkx/networkx), [llama-index](https://github.com/run-llama/llama_index), [llama-index-core](https://github.com/run-llama/llama_index), [langchain](https://github.com/langchain-ai/langchain), [langchain-core](https://github.com/langchain-ai/langchain) and [langgraph](https://github.com/langchain-ai/langgraph) to permit the latest version. Updates `uvicorn` to 0.54.0 - [Release notes](https://github.com/Kludex/uvicorn/releases) - [Changelog](https://github.com/Kludex/uvicorn/blob/main/docs/release-notes.md) - [Commits](Kludex/uvicorn@0.53.0...0.54.0) Updates `sqlalchemy` to 2.1.0 - [Release notes](https://github.com/sqlalchemy/sqlalchemy/releases) - [Changelog](https://github.com/sqlalchemy/sqlalchemy/blob/main/CHANGES.rst) - [Commits](https://github.com/sqlalchemy/sqlalchemy/commits) Updates `greenlet` to 3.5.6 - [Changelog](https://github.com/python-greenlet/greenlet/blob/master/CHANGES.rst) - [Commits](python-greenlet/greenlet@3.1.0...3.5.6) Updates `anthropic` to 1.8.0 - [Release notes](https://github.com/anthropics/anthropic-sdk-python/releases) - [Changelog](https://github.com/anthropics/anthropic-sdk-python/blob/main/CHANGELOG.md) - [Commits](anthropics/anthropic-sdk-python@v1.6.0...v1.8.0) Updates `boto3` to 1.43.102 - [Release notes](https://github.com/boto/boto3/releases) - [Commits](boto/boto3@1.43.97...1.43.102) Updates `networkx` to 3.7 - [Release notes](https://github.com/networkx/networkx/releases) - [Commits](networkx/networkx@networkx-3.6.1...networkx-3.7) Updates `llama-index` to 0.14.25 - [Release notes](https://github.com/run-llama/llama_index/releases) - [Changelog](https://github.com/run-llama/llama_index/blob/main/CHANGELOG.md) - [Commits](run-llama/llama_index@v0.14.24...v0.14.25) Updates `llama-index-core` to 0.14.25 - [Release notes](https://github.com/run-llama/llama_index/releases) - [Changelog](https://github.com/run-llama/llama_index/blob/main/CHANGELOG.md) - [Commits](run-llama/llama_index@v0.14.24...v0.14.25) Updates `langchain` to 1.4.2 - [Release notes](https://github.com/langchain-ai/langchain/releases) - [Commits](langchain-ai/langchain@langchain==1.4.1...langchain==1.4.2) Updates `langchain-core` to 1.6.5 - [Release notes](https://github.com/langchain-ai/langchain/releases) - [Commits](langchain-ai/langchain@langchain-core==1.6.3...langchain-core==1.6.5) Updates `langgraph` to 1.2.12 - [Release notes](https://github.com/langchain-ai/langgraph/releases) - [Commits](langchain-ai/langgraph@1.2.11...1.2.12) --- updated-dependencies: - dependency-name: uvicorn dependency-version: 0.54.0 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: sqlalchemy dependency-version: 2.1.0 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: greenlet dependency-version: 3.5.6 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: anthropic dependency-version: 1.8.0 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: boto3 dependency-version: 1.43.102 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: networkx dependency-version: '3.7' dependency-type: direct:production dependency-group: all-dependencies - dependency-name: llama-index dependency-version: 0.14.25 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: llama-index-core dependency-version: 0.14.25 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: langchain dependency-version: 1.4.2 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: langchain-core dependency-version: 1.6.5 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: langgraph dependency-version: 1.2.12 dependency-type: direct:production dependency-group: all-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
backend
dependencies
dependabot
Bot
added
backend
dependencies
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Repository: mrveiss/AutoBot-AI/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Retargeted to |
…ndencies-e8f513c62d
Review: do not merge as-is — and the obvious way to green the gate reintroduces 27 test failuresRead-only review, posted on the PR rather than relayed because the session that requested it has ended. Verified against The gate verdict
This PR raises floors in Four of the five are fixed one way. The fifth is fixed the opposite way.
Because the PR raises the pin and leaves the comment intact, merging it would put a file on This is the second occurrence. #17706 did exactly the same thing to the same package against the same recorded decision and was restored. The cause is not bad luck: the dependabot ignore entry uses greenlet is genuinely open
The six remaining updates are cleanboto3, networkx 3.6.1→3.7, llama-index and llama-index-core 0.14.24→0.14.25, langchain-core 1.6.3→1.6.5, langgraph 1.2.11→1.2.12. None appears in the gate; each is single-declared or Two cautions for whoever picks this upThe red is not the 27 failures. CI installed
StateStill |
Correction to my review: greenlet is not coupled to the sqlalchemy decisionMy review above put greenlet in the table as "coupled — see below" and said its floor could not be settled until the sqlalchemy question was. That framing is wrong, and a peer session caught it. Verified from the guard's own docstring before accepting the correction:
So #17432 is about availability, not version compatibility. The point is that a service using the async engine must declare greenlet itself, whatever SQLAlchemy does. That makes the greenlet floor raise independent of whether sqlalchemy is held at 2.0.x:
The Nothing else in the review changes. The five below-floor packages, the sqlalchemy revert, and the central warning all stand — and the warning is now sharper, because four of the five below-floor packages get their CI pin raised and only sqlalchemy is the exception:
I flagged greenlet as open rather than guessing at it, which was right, but "coupled" was a stronger claim than I had evidence for and it pointed at the wrong mechanism. |
…he four real floors (#17711) The grouped bump raised `sqlalchemy` to `>=2.1.0,<2.2` while leaving the comment directly above it intact — "Capped below 2.1 (#17445) ... 27 tests died inside its own cache-key machinery ... Do not raise this bound without running the SLM suite against 2.1.x first." Merging it would have put a file on `main` whose comment forbids its own pin. Second occurrence after #17706. Root cause is not in this file: the dependabot ignore is keyed on `update-types: semver-major`, and 2.0 -> 2.1 is a MINOR, so the rule cannot catch it. The durable fix is a `versions: [">=2.1"]` ignore on #17451, still open. Recorded in the cap comment so the next reader does not re-derive it and knows to expect a third attempt. The floor gate names five below-floor packages and only four are genuinely behind. Raising sqlalchemy's CI pin as part of a uniform repair is what reintroduces the 27 failures, so it is the one exception: requirements-ci/framework.txt uvicorn 0.53.0 -> 0.54.0 requirements-ci/ai-ml.txt anthropic 1.6.0 -> 1.8.0 requirements-ci/langchain.txt langchain 1.4.1 -> 1.4.2 requirements-ci/storage.txt greenlet 3.3.2 -> 3.5.6 requirements-ci/storage.txt sqlalchemy 2.0.54 — DELIBERATELY UNCHANGED greenlet moves with the bump because #17432 is about availability, not version coupling: SQLAlchemy ships it as an `[asyncio]` extra and under a `platform_machine` marker, it stopped arriving on 2026-09-24, and every `docker-smoke-test` failed on `main` with `ModuleNotFoundError`. The "-- see the note above" comment explains why greenlet is declared at all, not that its version tracks SQLAlchemy's, so holding sqlalchemy does not hold it. The other six updates in the group (boto3, networkx, llama-index, llama-index-core, langchain-core, langgraph) have no `requirements-ci/` pin and raise no floor question. Left as dependabot set them. Refs #17445, #17451
Fixed in
|
| file | package | change |
|---|---|---|
autobot-backend/requirements.txt |
sqlalchemy |
restored to >=2.0.54,<2.1 |
requirements-ci/framework.txt |
uvicorn |
0.53.0 -> 0.54.0 |
requirements-ci/ai-ml.txt |
anthropic |
1.6.0 -> 1.8.0 |
requirements-ci/langchain.txt |
langchain |
1.4.1 -> 1.4.2 |
requirements-ci/storage.txt |
greenlet |
3.3.2 -> 3.5.6 |
requirements-ci/storage.txt |
sqlalchemy |
2.0.54 — deliberately unchanged |
Raising sqlalchemy's CI pin is the obvious uniform repair and is the one that reintroduces the 27 failures in its cache-key machinery. It is the exception, not an oversight.
On greenlet, correcting the framing rather than the conclusion. Its floor moves with the bump. #17432 is about availability, not version coupling: SQLAlchemy ships it as an [asyncio] extra and, in some releases, under a platform_machine marker, it stopped arriving on 2026-09-24, and every docker-smoke-test on main failed with ModuleNotFoundError before the container could start. The -- see the note above comment explains why greenlet is declared at all; it does not say its version tracks SQLAlchemy's. So holding sqlalchemy at 2.0.x does not hold greenlet, and its CI pin mirrors the backend floor as #17432 intends.
Untouched: the other six updates in the group (boto3, networkx, llama-index, llama-index-core, langchain-core, langgraph) have no requirements-ci/ pin, so they raise no floor question and are left as dependabot set them.
Verified before pushing rather than after: the pre-commit pin-parity gate ("A requirements file and its include must not pin a package differently", #14228) passed, and the pre-push suite passed.
Reporting the verdict rather than merging — I am not the merger here. Refs #17445, #17451.
The new red is base — and the half this PR could affect passed
The Python audit — the only part a Python dependency PR can move — passed: The failure is the frontend npm audit: This cannot be this PR's doing. Its changed files are exactly five, all Python: No axios is a third advisory, newer than the known pair. The standing note on this PR was that the frontend audit carried two high advisories, A caution for the next reader of this log. The gate's one-line error says "3 unallowed" while the step summary's first lines name only two packages unless you read far enough for Consequence for this PR: it cannot go green on its own. The dependency-pin work on it is complete and correct — Read-only review; I have not touched the branch or the claim. |
…ndencies-e8f513c62d
…s missed (#17711) Three reds, three planes, one mistake repeated: I checked `requirements-ci/` with a pattern that assumed a pin FORM, and read the empty result as "nothing owed" rather than "my pattern did not match". code-quality -> "Audit requirements-ci for silent drift" (#14551/#17448) --------------------------------------------------------------------- `langchain-core` and `llama-index-core` ARE declared in `requirements-ci/`, as `>=` ranges rather than `==` pins: requirements-ci/langchain.txt langchain-core>=1.6.3 -> >=1.6.5 requirements-ci/llama-index.txt llama-index-core>=0.14.24 -> >=0.14.25 My first sweep grepped `^<pkg>==` and found nothing for both, so I reported "no CI pin exists, nothing owed". The audit compares declared PAIRS and flags constraints that can resolve to different releases, which is exactly what a raised production floor against an unraised CI range does. python-suite shard 5/12 -> requirements_floor_pairs_15661_test -------------------------------------------------------------- A THIRD plane: `docs/guides/requirements-local.txt` is a shipped manifest the guard pairs against `autobot-backend/requirements.txt` for `fastapi` and `uvicorn`. Raised `uvicorn[standard]>=0.53.0 -> >=0.54.0` there. Missed for the same reason plus one more: the docs manifest carries `uvicorn[standard]`, so a `^uvicorn[=<>]` pattern does not match it either. The guard says it in its own failure text -- "a shipped manifest's security floor bump must be mirrored here, not just where CI happens to look" -- and `where CI happens to look` is precisely the boundary my check drew. Not in scope here ----------------- The guard's second pair, `windows-npu-worker/requirements.txt` against `requirements-npu.txt`, is #17708's surface. Both currently read `uvicorn[standard]>=0.53.0`, so they agree today and whichever PR raises one must raise both. `Dependency Security Scan` stays red on the base-wide `brace-expansion` and `undici` advisories (#15467), which no change on this branch can clear. Refs #14551, #15661, #17448
…ain/all-dependencies-e8f513c62d' into dep-17711-local
…ndencies-e8f513c62d
…2.0 (#17709) Two reversals in one grouped bump, each left with its own contradicting context. sqlalchemy ---------- Raised to `>=2.1.0,<2.2` while the cap comment four lines above still read "Capped below 2.1 (#17445) ... 27 tests died inside its own cache-key machinery ... Do not raise this bound without running the SLM suite against 2.1.x first." Restored. This is the THIRD occurrence -- #17706, #17711, now this one -- and the ignore rule cannot catch any of them because it is keyed on `update-types: semver-major` while 2.0 -> 2.1 is a minor. Durable fix is a `versions: [">=2.1"]` ignore on #17451, still open; recorded in the comment so the file carries its own warning. huggingface-hub --------------- Raised to `>=2.0.0`, a major boundary, in one of THREE files declaring it -- `autobot-tts-worker/requirements.txt:8` (spelled `huggingface_hub`) and `autobot-infrastructure/autobot-npu-worker/docker/requirements-npu.txt:26` both stayed at `>=1.32.0`. The ai-stack container would have resolved 2.x while the other two resolved 1.x. Held, because CI cannot see whether it breaks. The only production call is `huggingface_hub.login(token=..., add_to_git_credential=False)` in two tts-worker ansible templates, and `autobot-tts-worker/tests/test_hf_token.py:101` swaps the whole module for a MagicMock, which accepts any signature -- so the assertion passes whatever 2.x does to that function, and rendered templates are imported by no test. Whether the signature is still valid in 2.x is UNKNOWN and not answerable from this repo; filed as #17847 with that stated rather than guessed. Left as dependabot set them --------------------------- langchain 1.4.2, langchain-core 1.6.5, llama-index 0.14.25, llama-index-core 0.14.25, uvicorn[standard] 0.54.0, googleapis-common-protos 1.75.4 -- all minor or patch. The `requirements-ci/` pins those need (langchain 1.4.2, uvicorn 0.54.0) are raised on #17711 rather than duplicated here, so this branch must rebase after that lands. Editing the same CI files from two open PRs is the conflict the one-PR-per-file rule exists to prevent. Refs #17445, #17451, #17847
…ndencies-e8f513c62d
…re/shared/docker/ai-stack with 8 updates (#17709) * chore(deps): bump the all-dependencies group Updates the requirements on [langchain](https://github.com/langchain-ai/langchain), [langchain-core](https://github.com/langchain-ai/langchain), [llama-index](https://github.com/run-llama/llama_index), [llama-index-core](https://github.com/run-llama/llama_index), [huggingface-hub](https://github.com/huggingface/huggingface_hub), [uvicorn](https://github.com/Kludex/uvicorn), [googleapis-common-protos](https://github.com/googleapis/google-cloud-python) and [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) to permit the latest version. Updates `langchain` to 1.4.2 - [Release notes](https://github.com/langchain-ai/langchain/releases) - [Commits](langchain-ai/langchain@langchain==1.4.1...langchain==1.4.2) Updates `langchain-core` to 1.6.5 - [Release notes](https://github.com/langchain-ai/langchain/releases) - [Commits](langchain-ai/langchain@langchain-core==1.6.3...langchain-core==1.6.5) Updates `llama-index` to 0.14.25 - [Release notes](https://github.com/run-llama/llama_index/releases) - [Changelog](https://github.com/run-llama/llama_index/blob/main/CHANGELOG.md) - [Commits](run-llama/llama_index@v0.14.24...v0.14.25) Updates `llama-index-core` to 0.14.25 - [Release notes](https://github.com/run-llama/llama_index/releases) - [Changelog](https://github.com/run-llama/llama_index/blob/main/CHANGELOG.md) - [Commits](run-llama/llama_index@v0.14.24...v0.14.25) Updates `huggingface-hub` to 2.0.0 - [Release notes](https://github.com/huggingface/huggingface_hub/releases) - [Commits](huggingface/huggingface_hub@v1.32.0...v2.0.0) Updates `uvicorn` to 0.54.0 - [Release notes](https://github.com/Kludex/uvicorn/releases) - [Changelog](https://github.com/Kludex/uvicorn/blob/main/docs/release-notes.md) - [Commits](Kludex/uvicorn@0.53.0...0.54.0) Updates `googleapis-common-protos` to 1.75.4 - [Release notes](https://github.com/googleapis/google-cloud-python/releases) - [Changelog](https://github.com/googleapis/google-cloud-python/blob/main/packages/google-cloud-documentai/CHANGELOG.md) - [Commits](googleapis/google-cloud-python@googleapis-common-protos-v1.75.3...googleapis-common-protos-v1.75.4) Updates `sqlalchemy` to 2.1.0 - [Release notes](https://github.com/sqlalchemy/sqlalchemy/releases) - [Changelog](https://github.com/sqlalchemy/sqlalchemy/blob/main/CHANGES.rst) - [Commits](https://github.com/sqlalchemy/sqlalchemy/commits) --- updated-dependencies: - dependency-name: langchain dependency-version: 1.4.2 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: langchain-core dependency-version: 1.6.5 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: llama-index dependency-version: 0.14.25 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: llama-index-core dependency-version: 0.14.25 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: huggingface-hub dependency-version: 2.0.0 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: uvicorn dependency-version: 0.54.0 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: googleapis-common-protos dependency-version: 1.75.4 dependency-type: direct:production dependency-group: all-dependencies - dependency-name: sqlalchemy dependency-version: 2.1.0 dependency-type: direct:production dependency-group: all-dependencies ... Signed-off-by: dependabot[bot] <support@github.com> * fix(deps): restore the sqlalchemy cap and hold huggingface-hub below 2.0 (#17709) Two reversals in one grouped bump, each left with its own contradicting context. sqlalchemy ---------- Raised to `>=2.1.0,<2.2` while the cap comment four lines above still read "Capped below 2.1 (#17445) ... 27 tests died inside its own cache-key machinery ... Do not raise this bound without running the SLM suite against 2.1.x first." Restored. This is the THIRD occurrence -- #17706, #17711, now this one -- and the ignore rule cannot catch any of them because it is keyed on `update-types: semver-major` while 2.0 -> 2.1 is a minor. Durable fix is a `versions: [">=2.1"]` ignore on #17451, still open; recorded in the comment so the file carries its own warning. huggingface-hub --------------- Raised to `>=2.0.0`, a major boundary, in one of THREE files declaring it -- `autobot-tts-worker/requirements.txt:8` (spelled `huggingface_hub`) and `autobot-infrastructure/autobot-npu-worker/docker/requirements-npu.txt:26` both stayed at `>=1.32.0`. The ai-stack container would have resolved 2.x while the other two resolved 1.x. Held, because CI cannot see whether it breaks. The only production call is `huggingface_hub.login(token=..., add_to_git_credential=False)` in two tts-worker ansible templates, and `autobot-tts-worker/tests/test_hf_token.py:101` swaps the whole module for a MagicMock, which accepts any signature -- so the assertion passes whatever 2.x does to that function, and rendered templates are imported by no test. Whether the signature is still valid in 2.x is UNKNOWN and not answerable from this repo; filed as #17847 with that stated rather than guessed. Left as dependabot set them --------------------------- langchain 1.4.2, langchain-core 1.6.5, llama-index 0.14.25, llama-index-core 0.14.25, uvicorn[standard] 0.54.0, googleapis-common-protos 1.75.4 -- all minor or patch. The `requirements-ci/` pins those need (langchain 1.4.2, uvicorn 0.54.0) are raised on #17711 rather than duplicated here, so this branch must rebase after that lands. Editing the same CI files from two open PRs is the conflict the one-PR-per-file rule exists to prevent. Refs #17445, #17451, #17847 * fix(ansible): follow langchain-core to 1.6.5 so the parity guard holds (#17709) `python-suite shard 9/12` was red on `ansible_requirements_parity_test.py::test_every_cross_manifest_divergence_is_in_the_baseline`: autobot-slm-backend/ansible/roles/dependency_patching/defaults/main.yml::::langchain-core: ansible >=1.6.3,<2.0.0, ['<every manifest in the tree>'] state ['>=1.6.5,<2.0.0'] This PR is what completed the bump, which is why the failure appears here and not on `main`. Before it, `autobot-backend/requirements.txt` and `requirements-ci/langchain.txt` already said `>=1.6.5` while `requirements-ai.txt` and the ansible role both still said `1.6.3` -- so the ansible declaration agreed with at least one manifest and the guard stayed quiet. Moving `requirements-ai.txt` to `1.6.5` makes the agreement unanimous and leaves the ansible role as the sole dissenter. So the guard is not complaining about this bump; it is reporting that the ansible role was already behind and had been hidden by the one manifest that had not caught up yet. Fixed the declaration rather than the baseline, as the failure message demands: `ansible_pip_parity_baseline.txt` only shrinks, and adding a line to it would record the divergence as acceptable instead of removing it. Verified: `repo_tests/ansible_requirements_parity_test.py` -> 8 passed. --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Martins Veiss <martins.veiss@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1 participant
Updates the requirements on uvicorn, sqlalchemy, greenlet, anthropic, boto3, networkx, llama-index, llama-index-core, langchain, langchain-core and langgraph to permit the latest version.
Updates
uvicornto 0.54.0Release notes
Sourced from uvicorn's releases.
Changelog
Sourced from uvicorn's changelog.
... (truncated)
Commits
3eb9a9aVersion 0.54.0 (#3161)cd7ef6dRemove races from supervisor tests (#3134)a56c7ccSupport HTTP/2 response trailers (#3146)9bd4404chore(deps): bump anyio from 4.13.0 to 4.14.2 (#3145)21f39efAdd HTTP/2 Early Hints support (#3137)Updates
sqlalchemyto 2.1.0Release notes
Sourced from sqlalchemy's releases.
... (truncated)
Commits
Updates
greenletto 3.5.6Changelog
Sourced from greenlet's changelog.
... (truncated)
Commits
abfe740Preparing release 3.5.6e23e3e4Change note for #5298de830fMerge pull request #529 from Georggi/patch-172d7cacMerge pull request #530 from python-greenlet/dependabot/github_actions/github...ac01b7dBump github/codeql-action in the github-actions groupe18f5a6Simplify GCDisabledGuard constructor6aaf3afBack to development: 3.5.6ddb1453Preparing release 3.5.57de515cUpdate CHANGES: Credit for issue 525 and note about 3.15 binary wheels [skip ci]f3746aaMerge pull request #526 from stickerdaniel/windows-static-runtimeUpdates
anthropicto 1.8.0Release notes
Sourced from anthropic's releases.
Changelog
Sourced from anthropic's changelog.
... (truncated)
Commits
4421d56Merge pull request #1946 from anthropics/release-please--branches--main--chan...d0247c2release: 1.8.0be01ed6chore(internal): remove mypy06d0a6bfix(tools): add_tools() takes effect straight away (#874)af029bdfix(streaming): avoid a Python 3.13 crash at exit when a stream is left open4687310fix(tools): leave reply-only params off the tool runner's compaction request ...b5cc700feat(api): add support for claude-opus-5-5, inline tool definitions and MCP t...70c8cbdchore(internal): fix tests539422crefactor(client): remove the request param transform in favour of the JSON en...10a4c07codegen metadataUpdates
boto3to 1.43.102Commits
da00dd2Merge branch 'release-1.43.102'551d660Bumping version to 1.43.102f63e52eAdd changelog entries from botocorea1acf79Merge branch 'release-1.43.101'931d5a2Merge branch 'release-1.43.101' into develop8c719efBumping version to 1.43.1017a0087dAdd changelog entries from botocore50dcfb2Bump the github-actions group across 1 directory with 4 updates (#4853)b9fcb18Bump https://github.com/astral-sh/ruff-pre-commit (#4849)2b8c4edMerge branch 'release-1.43.100'Updates
networkxto 3.7Release notes
Sourced from networkx's releases.
... (truncated)
Commits
49ca229Designate 3.7 releasebd45cfeUpdate minimum dependencies (SPEC 0) (#8916)fee1ebcBump release version4106c33Designate 3.7rc0 release083e472BUG: Hold the graph weakly in cached edge and degree views (#8892)8977f1cMerge pull request #8896 from jarrodmillman/py3.152d91736Remove failing tests0d6ac7amake lint happy9ca76bfmove python_rc to py315 specific featuresccf0995Support for Py3.15Updates
llama-indexto 0.14.25Release notes
Sourced from llama-index's releases.
... (truncated)
Changelog
Sourced from llama-index's changelog.
... (truncated)
Commits
f12d46aRelease 0.14.25 (#23165)f475afdFix: restore compact and refine streaming (#22836)ac010a0Remove deprecated ipex-llm and optimum-intel IPEX integrations (#22406)c60937ddocs: Update VoyageAI page with new models (#22871)b4fdfdddocs: Update MongoDB Key-Value Stores section (#22870)b13d30cdocs: Minor edits MongoDB Document Stores section (#22869)1dec9dfdocs: Update MongoDB Index Store section (#22868)fd4a517docs: retire LlamaHub links (#23070)0f43c00Logan/make docs acutally build (#23061)aa27480remove stale api reference (#23059)Updates
llama-index-coreto 0.14.25Release notes
Sourced from llama-index-core's releases.
... (truncated)
Changelog
Sourced from llama-index-core's changelog.
... (truncated)
Commits
f12d46aRelease 0.14.25 (#23165)f475afdFix: restore compact and refine streaming (#22836)ac010a0Remove deprecated ipex-llm and optimum-intel IPEX integrations (#22406)c60937ddocs: Update VoyageAI page with new models (#22871)b4fdfdddocs: Update MongoDB Key-Value Stores section (#22870)b13d30cdocs: Minor edits MongoDB Document Stores section (#22869)1dec9dfdocs: Update MongoDB Index Store section (#22868)fd4a517docs: retire LlamaHub links (#23070)0f43c00Logan/make docs acutally build (#23061)aa27480remove stale api reference (#23059)Updates
langchainto 1.4.2Release notes
Sourced from langchain's releases.
Commits
a18de59release(langchain): 1.4.2 (#40621)5bf6a15fix(langchain): preserve model-generated tool calls in HITL tool call edits a...a893bbdchore(model-profiles): refresh model profile data (#40600)fd4f161chore(deps): bump soupsieve from 2.8.4 to 2.9 in /libs/text-splitters (#40579)3b81e02chore(deps): bump urllib3 from 2.7.0 to 2.8.0 in /libs/partners/chroma (#40582)fa369c9chore(deps): bump langsmith from 0.12.1 to 0.12.6 in /libs/partners/chroma (#...eb544d3chore(deps): bump urllib3 from 2.7.0 to 2.8.0 in /libs/partners/fireworks (#4...5e8888fchore(deps): bump filelock from 3.32.5 to 4.0.0 in /libs/partners/chroma (#40...a62361achore(deps): bump langsmith from 0.12.1 to 0.12.6 in /libs/partners/fireworks...e2d39c4chore(deps): bump pygments from 2.20.0 to 2.21.0 in /libs/partners/fireworks ...Updates
langchain-coreto 1.6.5Release notes
Sourced from langchain-core's releases.
Commits
c5ab14drelease(core): 1.6.5 (#40816)5704d9dchore(model-profiles): refresh model profile data (#40804)7622d3drelease(openai): 1.6.6 (#40800)2dd956bdocs(infra): fix AGENTS.md root setup guidance and package doc accuracy (#40794)49f4b40fix(openai): raise on error events in stream path (#40791)19cadaafix(core): abbreviate long tool IDs in XML buffer strings (#40792)798441echore(anthropic): fix integration test cassette (#40790)a476942release(openai): 1.6.5 (#40787)46c6bdfrelease(anthropic): 1.7.4 (#40786)290dabafix(anthropic): add Opus 5.5 and GPT-6 profile augmentations (#40785)Updates
langgraphto 1.2.12Release notes
Sourced from langgraph's releases.
Commits
49cce0crelease(sdk-py): 0.4.5 (#8988)19273farelease(langgraph): 1.2.12 (#8987)ed384f3fix(cli): remediate AnyIO vulnerabilities in example lockfiles (#9022)aa742fbchore(deps): bump anyio from 4.14.2 to 4.15.1 in /libs/sdk-py (#8997)b58044achore(deps): bump anyio from 4.13.0 to 4.14.2 in /libs/cli (#8998)daa514achore(deps): bump anyio from 4.13.0 to 4.14.2 in /l...Description has been truncated