Repository navigation
Qualify dependency upgrades and compatibility fixes for 26.10.1 - #343
Merged
Merged
Conversation
| from typing import TYPE_CHECKING, Any, cast | ||
|
|
||
| if TYPE_CHECKING: | ||
| from google.generativeai.types.text_types import BatchEmbeddingDict # pyright: ignore[reportMissingImports] |
| async with asyncio.timeout(10): | ||
| while not http.started: | ||
| if task.done(): | ||
| await task |
| await asyncio.wait_for(first_chunk.wait(), timeout=2) | ||
| task.cancel() | ||
| with pytest.raises(asyncio.CancelledError): | ||
| await task |
| raise ValueError("consumer stopped") | ||
| if ending == "cancel": | ||
| raise asyncio.CancelledError | ||
| except (ValueError, asyncio.CancelledError): |
This was referenced Oct 14, 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.
Dependency refresh and compatibility repairs
The 23 open Dependabot requests contain stale, overlapping updates. This change resolves them as one tested graph while preserving provider extras, HEIF support, the PostgreSQL namespace-write guarantee and the pgvector/HNSW backend.
The 26.10.1 candidate uses Pydantic AI 2.55, FastMCP 4.1, MCP 2.3, OpenAI 3.31 and Starlette 1.7, with compatible security fixes and immutable GitHub Action references. It repairs the renamed thinking-profile field, py7zr extraction API, HEIF registration, optional SDK typing/response contracts (including Mistral 2 client imports), and Chroma namespace-filter composition. Interrupted incremental streams now close native text iterators before their context exits, preventing a reproduced shutdown error.
README, installation and migration instructions, security guidance, changelog and the dependency resolution record describe the final behavior and account for every original request. Release builds exercise the declared PEP 517 backend and publish checksums automatically.
Validation
No paid model provider or shared application/database was used. Hosted CI and publication verification are separate final gates.
Remaining limitations
Six known optional-package advisories remain: two Ragas and four ChromaDB alerts, including critical Chroma server issues. They are explicitly documented with restrictions; none was dismissed. Newer Ragas cannot currently resolve with the required OpenAI SDK, and the inspected Chroma version has no published patch. This release does not claim zero vulnerabilities or tenant authorization from namespace metadata.
The Pydantic AI minimum is 2.53; rejected-attempt fallback accounting needs 2.55 or later. Aggregate token checks do not establish separate per-provider dollar attribution. Retained buffered text iterators have an upstream shutdown limitation also reproduced without Firefly; the repaired regression concerns incremental iterators.
Supersedes #334, #333, #332, #330, #329, #328, #327, #326, #325, #322, #321, #320, #319, #318, #317, #316, #313, #312, #311, #310, #308, #290 and #289. Their histories will be retained with a specific resolution comment after this PR merges.