Suggestion

#8602 (integration tests failing on themain branch) happened because integration tests install the latest version of upstream dependencies. The benefit of using latest versions is that we see failures as soon as possible. But the downside is thatmain can have failing tests unexpectedly.

I think we want to make sure themain branch is broken as little as possible. A couple strategies come to mind:

• Having the integration tests file a new issue when a new failure is detected: so we get notified via an issue of failures onmain
• Using pinned dependencies for the integration tests, and use Renovate/similar to auto-update them: so failures don't seep intomain

I'd prefer the latter, so thatmain doesn't break. Thoughts?