Bump haystack-ai from 2.5.0 to 2.31.0

[dependabot]

Bumps haystack-ai from 2.5.0 to 2.31.0.

Release notes

Sourced from haystack-ai's releases.

v2.31.0

⭐️ Highlights

📦 Slimming down Haystack core ahead of 3.0

This release begins the migration of many components out of haystack core and into dedicated integration packages, in preparation for Haystack 3.0. Components with heavy or optional dependencies — including all SentenceTransformers embedders and rankers, the Hugging Face API components, the legacy Generators, TikaDocumentConverter, AzureOCRDocumentConverter, the Whisper transcribers, the OpenAPI connectors, the spaCy and Transformers extractors/classifiers/routers, SerperDevWebSearch, SearchApiWebSearch, DocumentLanguageClassifier/TextLanguageRouter, and the Datadog and OpenTelemetry tracers — are now deprecated and will be removed in 3.0.

Each component continues to work as before for now, and moving to the new package is a one-line import change once you install it. See the Deprecation Notes below for the full list and per-component migration snippets. For example:

# Before
from haystack.components.embedders import SentenceTransformersTextEmbedder
After: pip install sentence-transformers-haystack
from haystack_integrations.components.embedders.sentence_transformers import SentenceTransformersTextEmbedder

🔀 Type-preserving routing with ConditionalRouter

ConditionalRouter now accepts an output_passthrough: True flag on a route. When set, the route's output is treated as a plain variable name rather than a Jinja2 template, and the value is passed straight through from the pipeline inputs. This lets you route complex, non-basic types such as dataclasses and Pydantic models without the Jinja2 rendering silently converting them to their string representation.

from haystack.components.routers import ConditionalRouter
routes = [
{
"condition": "{{query.intent == 'search'}}",
"output": "query",            # variable name, not a Jinja2 template
"output_name": "search_query",
"output_type": ParsedQuery,
"output_passthrough": True,
},
]
router = ConditionalRouter(routes)
result = router.run(query=query)
assert result["search_query"] is query   # same object, type preserved

⬆️ Upgrade Notes

• DocumentNDCGEvaluator now matches documents by their content field by default instead of their auto-generated id. Previously, ground truth and retrieved documents were matched only if they had identical id values, which rarely happened in practice since IDs are generated independently for each Document instance. As a result, NDCG scores computed with this evaluator may change for existing pipelines. To keep the previous id-based matching behavior, pass document_comparison_field="id" when constructing the evaluator.

🚀 New Features

• Added native asynchronous support (run_async) to LLMEvaluator, FaithfulnessEvaluator, and ContextRelevanceEvaluator. This allows concurrent evaluation loops inside async applications like FastMCP or FastAPI without blocking the main event loop, while automatically falling back to thread workers for synchronous chat generators.
• Added optional YAML frontmatter extraction to MarkdownToDocument. When initialized with extract_frontmatter=True, YAML frontmatter at the beginning of a Markdown file is removed from the converted content and added to Document.meta.

⚡️ Enhancement Notes

... (truncated)

Commits

• df44022 bump version to 2.31.0
• f0f1aef bump version to 2.31.0-rc2
• afdb998 Revert "fix: updating generated answer and extracted answers serialisation (#...
• 0f04657 bump version to 2.31.0-rc1
• 23b719d build(deps): bump oss-fuzz-base/base-builder-python from 53d5573 to `6768b6...
• 618be9e build(deps): bump docker/setup-buildx-action from 4.1.0 to 4.2.0 (#11887)
• 9e974c4 docs: sync Haystack API reference on Docusaurus (#11884)
• b25f5d8 fix: update Multiretriever params (#11823)
• b4b2843 docs: sync Haystack API reference on Docusaurus (#11882)
• f7fec32 fix: respect ByteStream encoding in HTMLToDocument and MarkdownToDocument (#1...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)