ci: make nightly tests actually run with Haystack main branch

[anakin87]

Related Issues

After the release of the new ChatMessage in deepset-ai/haystack#8640, I was expecting several failures in the nightly tests with Haystack main.

Indeed, I encountered these failures locally by executing the following steps:

...
 cd "$dir"
hatch env prune
hatch run uv pip install git+https://github.com/deepset-ai/haystack.git
hatch run uv pip freeze

However the nightly CI tests did not fail... 🤔

Then I realized what's the difference:

haystack-core-integrations/.github/workflows/amazon_bedrock.yml

Line 84 in 3a3419a

hatch run pip install git+https://github.com/deepset-ai/haystack.git

We are not using uv there, so the tests don't run with Haystack main, but with the latest stable release.

Proposed Changes:

• use uv to install Haystack main in the test environment

How did you test it?

Local tests, CI

Notes for the reviewer

Failing tests are unrelated to this PR

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.

[julian-risch]

@anakin87 To explicitly install from main, we should use pip install git+https://github.com/deepset-ai/haystack.git@main with @main at the end. Using uv sounds good too. So I'd suggest changing all lines to hatch run uv pip install git+https://github.com/deepset-ai/haystack.git@main.

[anakin87]

@julian-risch I incorporated your feedback.
Just to clarify about uv: using uv is important because our hatch environment uses it as an installer, so if we don't install Haystack main using it, the tests are not run using the main branch.

[julian-risch]

LGTM! 👍