chore(deps-dev): bump haystack-ai from 2.1.2 to 2.2.4 in /packages/opentelemetry-instrumentation-haystack

[dependabot]

Bumps haystack-ai from 2.1.2 to 2.2.4.

Release notes

Sourced from haystack-ai's releases.

v2.2.4

Release Notes

v2.2.4

⚡️ Enhancement Notes

• Added the apply_filter_policy function to standardize the application of filter policies across all document store-specific retrievers, allowing for consistent handling of initial and runtime filters based on the chosen policy (replace or merge).
• Introduced a 'filter_policy' init parameter for both InMemoryBM25Retriever and InMemoryEmbeddingRetriever, allowing users to define how runtime filters should be applied with options to either 'replace' the initial filters or 'merge' them, providing greater flexibility in filtering query results.

🐛 Bug Fixes

• Meta handling of bytestreams in Azure OCR has been fixed.
• Fix some bugs running a Pipeline that has Components with conditional outputs. Some branches that were expected not to run would run anyway, even if they received no inputs. Some branches instead would cause the Pipeline to get stuck waiting to run that branch, even if they received no inputs. The behaviour would depend whether the Component not receiving the input has a optional input or not.

v2.2.4-rc1

Release Notes

v2.2.4-rc1

⚡️ Enhancement Notes

• Added the apply_filter_policy function to standardize the application of filter policies across all document store-specific retrievers, allowing for consistent handling of initial and runtime filters based on the chosen policy (replace or merge).
• Introduced a 'filter_policy' init parameter for both InMemoryBM25Retriever and InMemoryEmbeddingRetriever, allowing users to define how runtime filters should be applied with options to either 'replace' the initial filters or 'merge' them, providing greater flexibility in filtering query results.

🐛 Bug Fixes

• Fix some bugs running a Pipeline that has Components with conditional outputs. Some branches that were expected not to run would run anyway, even if they received no inputs. Some branches instead would cause the Pipeline to get stuck waiting to run that branch, even if they received no inputs. The behaviour would depend whether the Component not receiving the input has a optional input or not.

v2.2.3

Release Notes

v2.2.3

🐛 Bug Fixes

• Pin numpy<2 to avoid breaking changes that cause several core integrations to fail. Pin tenacity too (8.4.0 is broken).

⚡️ Enhancement Notes

• Export ChatPromptBuilder in builders module

v2.2.2

Release Notes

v2.2.2

🐛 Bug Fixes

• Add missing metrics column in DataFrame returned by EvaluationRunResult.score_report()

... (truncated)

Commits

• 777e6f5 Bump version to 2.2.4
• ce8af3f fix: meta from ByteStream input for AzureOCRDocumentConverter (#7955)
• 2be576f Bump version: use the right version format
• 717279b Bump version to v2.2.4-rc1
• 4cffd39 feat: Add apply_filter_policy function (#7902)
• ac9b02f feat: Add filter_policy init parameter to in memory retrievers (#7795)
• d3cdbcc fix: Fix running Pipeline with conditional branch and Component with defaul...
• 3194785 Bump version to 2.2.3
• 8abd5d8 export ChatPromptBuilder and add it to pydoc config (#7796)
• 0e112dd chore: pin numpy<2; tenacity!=8.4.0 (#7876)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[dependabot]

The following labels could not be found: opentelemetry-instrumentation-haystack.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.