test: run test suites against Haystack v3 branch (do not merge)#3532
Draft
julian-risch wants to merge 1 commit into
Draft
test: run test suites against Haystack v3 branch (do not merge)#3532julian-risch wants to merge 1 commit into
julian-risch wants to merge 1 commit into
Conversation
Point every integration's haystack-ai dependency at the v3 draft branch to surface incompatibilities ahead of the 3.0 release. Reruns and fail-fast are removed from unit-cov-retry so CI reports all failures. Not meant to be merged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
Contributor
This was referenced Jul 2, 2026
Merged
Open
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.
Related Issues
v3branch against haystack-core-integrations)Proposed Changes:
haystack-aidependency of all 92 integrations at the Haystackv3draft branch (haystack-ai @ git+https://github.com/deepset-ai/haystack.git@v3) so every integration's CI workflow runs against the 3.0 draft[tool.hatch.metadata] allow-direct-references = truewhere missing, so hatch accepts the git dependency--reruns 3 --reruns-delay 30 -xfrom theunit-cov-retryscript so CI reports all unit-test failures instead of stopping at the first oneThis follows the approach from #3467, extended to all integrations and targeting
v3instead oflifecycle.How did you test it?
Verified locally for the
anthropicintegration that hatch resolves and installs Haystack from thev3branch and that the unit tests run. Two tests already fail there against v3 (test_to_dict_with_parameters,test_serde_in_pipeline— serialization output differences), which is exactly the kind of incompatibility this PR is meant to surface.Notes for the reviewer
The CI results on this PR are the deliverable: each integration's workflow shows which test suites break against the v3 draft.
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:.🤖 Generated with Claude Code