Add Dependabot Cooldown#13
Merged
Merged
Conversation
skyguy94
approved these changes
May 20, 2026
skyguy94
left a comment
There was a problem hiding this comment.
This adds support for dependabot package updates. Those are different than dependabot security updates. One path is for vulnerabilities and the other is for bugs.
If you want automatic package updates, then this is fine.
Collaborator
Author
|
Since this is a public demo, I do think it's worth keeping the packages up to date. I dialed back the frequency to monthly though because we don't need to be quite so aggressive. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Add a dependabot cooldown, same as CareEvolution/MyDataHelpsUI#610
Security
REMINDER: All file contents are public.
Describe briefly what security risks you considered, why they don't apply, or how they've been mitigated.
Consider "Squash and merge" as needed to keep the commit history reasonable on
main.Reviewers
Assign to the appropriate reviewer(s). Minimally, a second set of eyes is needed ensure no non-public information is published. Consider also including: