[Test/WIP] feat: check compatibility

[ArzelaAscoIi]

Related Issues

• fixes #issue-number

Proposed Changes:

How did you test it?

Notes for the reviewer

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:.

[silvanocerza]

We shouldn't do this.

It's a mess that we decided we wanted to avoid completely with Haystack 2 and that's why we have the integrations completely separate.

This is a huge amount of work and creates a huge amount of conflicts and problems that we can't tackle in any way.

[wochinge]

It's a mess that we decided we wanted to avoid completely with Haystack 2 and that's why we have the integrations completely separate.

Fair point. However, when we talked to @shadeMe suggested otherwise. The test seems like a pretty simple way to at least be aware of conflicts.

[wochinge]

@ArzelaAscoIi Talked to Madeesh about this. Let's try it out in our pipeline-images repo. Depending on whether there is any problem in the first place, we can reevaluate what the best way forward is (e.g. if there is a simple maintainable fix or if we need to change our approach for building the images).

Based on the experience in our repository we can then probably also give better input on how much maintenance effort a similar check in this repository would be.

[ArzelaAscoIi]

Sure! Sounds good