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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
GitHub Dependabot configuration cooldown default-days range exclude wildcard cooldown💡 Result:
As of July 31, 2026, GitHub Dependabot applies a default 3-day cooldown period to all version updates to allow new releases to stabilize before creating a pull request [1][2]. This default does not apply to security updates, which continue to be created immediately [3][1]. Key details regarding the
cooldownconfiguration include: Default Cooldown Behavior: - The 3-day default is applied automatically to all version updates if nocooldownblock is present in your.github/dependabot.ymlfile [1][4]. - You can override this by explicitly defining acooldownblock [2]. - The cooldown applies specifically to version updates; security updates are never delayed by this mechanism [3][5][6]. Configuration Range and Options: - The number of days for cooldown parameters (such asdefault-days) must be an integer between 1 and 90 [5][4]. - Supported parameters within thecooldownblock includedefault-days,semver-major-days,semver-minor-days, andsemver-patch-days(the latter three apply only to ecosystems supporting SemVer) [3][4]. Wildcard and Exclusion Rules: - Theincludeandexcludeoptions allow you to specify which dependencies the cooldown applies to [3]. - Bothincludeandexcludesupport wildcards (e.g.,pandas*) to match multiple dependencies [3][5]. - Each list supports up to 150 items [3][5]. - Theexcludelist always takes precedence over theincludelist [3]. If a dependency appears in both, it will be excluded from the cooldown and updated immediately [3]. Important Considerations: - Cooldown interacts with yourschedule.interval: Dependabot checks for updates based on your schedule, but a release only becomes eligible for a pull request once the cooldown period has elapsed [4]. - Theexcludelist forcooldownis distinct from the generalignoreconfiguration; whileignorecan prevent updates entirely or filter by version/type,cooldownspecifically delays the timing of the update [3][7].Citations:
🌐 Web query:
GitHub Dependabot configuration reference cool-downtime default-days value💡 Result:
As of July 31, 2026, the default behavior for Dependabot version updates includes a mandatory cooldown period of 3 days [1][2]. This means that a new dependency version is not considered for a version update until at least 3 days after its release [1][3]. Key details regarding the
default-daysvalue and cooldown configuration: * Default Value: If thecooldownblock is omitted from your.github/dependabot.ymlfile, Dependabot automatically applies a 3-day cooldown period [1][2]. * Security Updates: This default cooldown applies exclusively to version updates and does not affect security updates, which continue to be opened immediately to ensure critical fixes are not delayed [1][2][3]. * Customization: You can override the default by adding acooldownsection to your configuration file [2][3]. Thedefault-daysparameter accepts integer values between 1 and 90 [3][4]. * Configuration Usage:yaml updates: - package-ecosystem: "npm" directory: "/" schedule: interval: "daily" cooldown: default-days: 5 # Example: overriding the 3-day default* Interaction with SemVer: If you define specific SemVer-based cooldowns (semver-major-days,semver-minor-days,semver-patch-days), those settings will take precedence over thedefault-daysvalue [1][3]. This default cooldown was introduced by GitHub on July 14, 2026, to provide a safety window for new releases [2][5].Citations:
🏁 Script executed:
Repository: commit-check/commit-check-action
Length of output: 258
🏁 Script executed:
Repository: commit-check/commit-check-action
Length of output: 1051
Use a supported cooldown configuration for pip updates.
default-daysmust be an integer between 1 and 90. Setting0makes this update configuration invalid. If pip updates must not wait for the release-age delay, exclude the wildcard instead:Proposed fix
📝 Committable suggestion
🤖 Prompt for AI Agents