Conversation
Rename .disabled configs back and add minimumReleaseAge: 14 days Signed-off-by: Moe Zein <moe.zein@datadoghq.com>
434a00c to
7e58133
Compare
|
✨ Fix all issues with BitsAI or with Cursor
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3730 +/- ##
==========================================
- Coverage 68.90% 68.84% -0.06%
==========================================
Files 166 166
Lines 19015 19015
Branches 1792 1792
==========================================
- Hits 13102 13091 -11
- Misses 5101 5114 +13
+ Partials 812 810 -2
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
5a99fb4 to
7e58133
Compare
|
Closing and re-opening with corrected cooldown value (2 days instead of 14 days) and updated title/description. |
Note
Merge only if this is still needed and your repo is not managed by ADMS.
If your repository is already managed by ADMS, feel free to close or ignore this PR.
We are adding a mandatory 14-day cooldown (
minimumReleaseAge) on dependencies to reduce the risk of zero-day vulnerabilities.Please expect PRs that re-enable updaters and introduce the cooldown setting. If you notice any configurations that were not disabled on your repos, please ensure a cooldown is added.
If your repository is already managed by ADMS and no longer requires these configurations, feel free to close or ignore the PR.