You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all integrations are tested in PRs with the oldest version they support. This helps avoiding the introduction of breaking changes, but it relies on developers to test with recent versions.
We could add a new testing stage for PRs, that tests changes with an snapshot version.
The changes would be:
Add a stage that tests on PRs with an snapshot version of the stack, apart of the current stage that test with the oldest supported version.
Add an automation to open a PR to update the snapshot version used. Failures here should follow same strategy as Improve visibility on failures in daily job #6071. This automation could replace the daily job for latest snapshot.
This will basically duplicate the resources used to test each PR.
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!
Currently all integrations are tested in PRs with the oldest version they support. This helps avoiding the introduction of breaking changes, but it relies on developers to test with recent versions.
We could add a new testing stage for PRs, that tests changes with an snapshot version.
The changes would be:
This will basically duplicate the resources used to test each PR.
Related to #213
The text was updated successfully, but these errors were encountered: