related to #500 (there we explain why we prefer a reactive strategy over defensively pinning upper bounds on all dependencies.)
Idea:
- Add a scheduled CI job (e.g. weekly) that runs the test suite against the latest versions of dependencies.
- When a run fails, add an upper bound or adjust the code to work with the updated dependency
related to #500 (there we explain why we prefer a reactive strategy over defensively pinning upper bounds on all dependencies.)
Idea: