Add a default cooldown of 7 days for GitHub Action updates#553
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #553 +/- ##
==========================================
Coverage 71.20% 71.20%
Complexity 1150 1150
==========================================
Files 67 67
Lines 5563 5563
==========================================
Hits 3961 3961
Misses 1602 1602
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
What?
Adds a default cooldown of 7 days for GitHub Action updates via Dependabot.
Why?
Ensure Dependabot doesn't prompt us to update a package that was updated recently, leading to a higher risk for exploits.
See WordPress/performance#2277 for more details.
How?
Adds a cooldown config option for GitHub Action updates. Note we already have a cooldown option set for composer and npm updates
Use of AI Tools
None
Testing Instructions
n/a
Changelog Entry