Repository navigation
security: Delay dependabot updates [TAROT-3707] - #238
Conversation
7 days should be enough when most malicious packages are patched within 24 hours.
Up to standards ✅🟢 Issues
|
There was a problem hiding this comment.
Pull Request Overview
This Pull Request fails to meet its primary objective because it introduces a configuration property, cooldown, which is not supported by the GitHub Dependabot v2 schema. While the intent—to delay updates to mitigate supply-chain attacks—is valid, the implementation will result in a validation error that prevents Dependabot from functioning correctly in this repository. Although Codacy marked the PR as 'up to standards', the schema validation error is a blocker for merging.
About this PR
- The proposed 7-day cooldown cannot be implemented via standard
dependabot.ymlconfiguration as GitHub does not natively support release-delay filters. Using unsupported keys will cause Dependabot to ignore the configuration or fail to run.
Test suggestions
- Verify dependabot.yml schema validity against GitHub's official specification
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify dependabot.yml schema validity against GitHub's official specification
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
7 days should be enough when most malicious packages are patched within 24 hours.