-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Daily CI with unpinned deps #580
Comments
We can also add a weekly dependabot job? |
Daily also works (the previous PR is closed). |
That also works, but I also want daily CI for other things like testing a wider variety of versions as in #507 without slowing down PRs. |
I forgot that |
Reopening because based on https://github.com/orgs/community/discussions/25351 the current workflow will only send an email to a single person, which isn't loud enough. |
(I know there's a TODO in that file in the PR which is probably because of this, I hadn't noticed until merging) |
Following up on #576
At the bare minimum we need a job that runs daily with the latest versions of all dependencies so that we can detect breakages.
Previously regular CI ran with unpinned dependencies which forced us to fix the problem ASAP. That had downsides, but I want to keep the upsides. I want to have some kind of system so that when the job fails we treat it with similar urgency to before, so that new users aren't immediately faced with a critical error caused by an outstanding bug. Relevant developers should definitely get an email about the job failing, but that's not quite enough. I may miss the email in a sea of notifications, or I may think someone else will deal with it. For now let's just say that if any of us see that CI has failed we should open an urgent issue if there isn't one already, and check with the team what the plan is.
The text was updated successfully, but these errors were encountered: