[timjensen-wk]

Dependabot 4-day cooldown rollout

This PR is part of an org-wide rollout adding a JFrog Curation-aligned Dependabot cooldown policy:

• docker, docker-compose, devcontainers ecosystems: cooldown disabled entirely (cooldown: { exclude: ["*"] }) since these images don't route through Curation.
• github-actions: left untouched (no cooldown added if none existed; existing cooldown blocks preserved as-is).
• All other ecosystems: cooldown.default-days raised to a floor of 4 (existing values >= 4 were left untouched; nothing was silently lowered).

Config file: .github/dependabot.yml

Diff

diff --git a/.github/dependabot.yml b/.github/dependabot.yml
index d9a8ae1..434584c 100644
--- a/.github/dependabot.yml
+++ b/.github/dependabot.yml
@@ -15,4 +15,6 @@ updates:
       interval: weekly
     groups:
       pub:
-        patterns: ["*"]
\ No newline at end of file
+        patterns: ["*"]
+    cooldown:
+      default-days: 4
\ No newline at end of file

Automated change — please review and merge.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.