Now that we're using self-hosted CI runners, we should create a daily workflow that runs backwards-compatibility tests against more versions.
CI for PRs only test compatibility vs the oldest supported version (v0.2.1 as-of creating this issue). We originally decided to run against fewer versions to improve developer experience for PRs, but this makes it possible for backwards-incompatible changes to go undetected (see: https://github.com/fedimint/fedimint/pull/5171).
We should also consider other tests that don't fit within PR CI workflows but would be useful to run in daily workflows, e.g. upgrade tests, but that's outside the scope of this issue.
Now that we're using self-hosted CI runners, we should create a daily workflow that runs backwards-compatibility tests against more versions.
CI for PRs only test compatibility vs the oldest supported version (v0.2.1 as-of creating this issue). We originally decided to run against fewer versions to improve developer experience for PRs, but this makes it possible for backwards-incompatible changes to go undetected (see: https://github.com/fedimint/fedimint/pull/5171).
We should also consider other tests that don't fit within PR CI workflows but would be useful to run in daily workflows, e.g. upgrade tests, but that's outside the scope of this issue.
Other considerations: