-
Notifications
You must be signed in to change notification settings - Fork 14
Add scheduled regular tests to confirm version changes #385
Copy link
Copy link
Open
Labels
buildChanges that affect the build system or external dependencies (example scopes: hatch, setuptool)Changes that affect the build system or external dependencies (example scopes: hatch, setuptool)ciChanges to our CI configuration files and scripts (example scopes: Travis, Circle, Github Actions)Changes to our CI configuration files and scripts (example scopes: Travis, Circle, Github Actions)dependenciesPull requests that update a dependency filePull requests that update a dependency file
Description
Metadata
Metadata
Assignees
Labels
buildChanges that affect the build system or external dependencies (example scopes: hatch, setuptool)Changes that affect the build system or external dependencies (example scopes: hatch, setuptool)ciChanges to our CI configuration files and scripts (example scopes: Travis, Circle, Github Actions)Changes to our CI configuration files and scripts (example scopes: Travis, Circle, Github Actions)dependenciesPull requests that update a dependency filePull requests that update a dependency file
Type
Fields
Give feedbackNo fields configured for issues without a type.
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.