As caustics development slows down, it will be useful to have automated regular testing that no dependency changes have broken the package. A schedule CI run would be good. It could also be very helpful to have a regular CI run that checks for dependency version updates and runs the CI on the updated versions (even exceeding the version limits in our requirements.txt file) to see if caustics needs a dependency update.
As caustics development slows down, it will be useful to have automated regular testing that no dependency changes have broken the package. A schedule CI run would be good. It could also be very helpful to have a regular CI run that checks for dependency version updates and runs the CI on the updated versions (even exceeding the version limits in our
requirements.txtfile) to see if caustics needs a dependency update.