Skip to main content
Open source

Add cooldown periods to Dependabot configuration

Recipe IDorg.openrewrite.github.AddDependabotCooldown
Artifactorg.openrewrite.recipe:rewrite-github-actions

Adds a cooldown section to each update configuration in Dependabot files. Supports default-days, semver-major-days, semver-minor-days, semver-patch-days, include, and exclude options. This implements a security best practice where dependencies are not immediately adopted upon release, allowing time for security vendors to identify potential supply chain compromises. Cooldown applies only to version updates, not security updates. Read more about dependency cooldowns. The available configuration options for dependabot are listed on GitHub.

Single recipeOpenRewritegithubsecuritydependabotdependenciesModerne Source Available License
Try in PlatformTry this recipe in the Moderne platform. Not a user yet? You’ll get a no-setup demo environment, with nothing to install or configure.

Options

7 parameters
7 optional
ParameterExampleTypeRequired
cooldownDays7IntegerOptional
The number of days to wait before considering a published dependency suitable for use (1-90). This delay allows security vendors time to identify potential compromises. Applied to all version types unless specific semver options are set.
excludecritical-security-packageListOptional
List of up to 150 dependencies to exempt from cooldown. Supports wildcard patterns with *. Exclude list takes precedence over include list.
excludeEcosystemsgithub-actionsListOptional
List of ecosystems to be excluded
includelodash, react*ListOptional
List of up to 150 dependencies to apply cooldown to. Supports wildcard patterns with *. If not specified, cooldown applies to all dependencies.
semverMajorDays14IntegerOptional
The number of days to wait for major version updates (1-90). Only applies to package managers that support semantic versioning.
semverMinorDays7IntegerOptional
The number of days to wait for minor version updates (1-90). Only applies to package managers that support semantic versioning.
semverPatchDays3IntegerOptional
The number of days to wait for patch version updates (1-90). Only applies to package managers that support semantic versioning.

Examples

yaml
ParameterValue
cooldownDaysnull
semverMajorDaysnull
semverMinorDaysnull
semverPatchDaysnull
includenull
excludenull
excludeEcosystemsnull
Before
version: 2
updates:
- package-ecosystem: github-actions
directory: /
schedule:
interval: daily
- package-ecosystem: maven
directory: /
schedule:
interval: weekly
After
version: 2
updates:
- package-ecosystem: github-actions
directory: /
schedule:
interval: daily
cooldown:
default-days: 7
- package-ecosystem: maven
directory: /
schedule:
interval: weekly
cooldown:
default-days: 7

Usage

Run this recipe

This recipe has no required configuration options. Users of Moderne can run it via the Moderne CLI.

You will need to have configured the Moderne CLI on your machine before you can run the following command.

shell
mod run . --recipe AddDependabotCooldown

If the recipe is not available locally, then you can install it using:

mod config recipes jar install org.openrewrite.recipe:rewrite-github-actions:3.25.0

Data tables

Source files that had results
org.openrewrite.table.SourcesFileResults

Source files that were modified by the recipe run.

ColumnDescription
Source path before the runThe source path of the file before the run. null when a source file was created during the run.
Source path after the runA recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run.
Parent of the recipe that made changesIn a hierarchical recipe, the parent of the recipe that made a change. Empty if this is the root of a hierarchy or if the recipe is not hierarchical at all.
Recipe that made changesThe specific recipe that made a change.
Estimated time savingAn estimated effort that a developer to fix manually instead of using this recipe, in unit of seconds.
CycleThe recipe cycle in which the change was made.
Source files that had search results
org.openrewrite.table.SearchResults

Search results that were found during the recipe run.

ColumnDescription
Source path of search result before the runThe source path of the file with the search result markers present.
Source path of search result after run the runA recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run.
ResultThe trimmed printed tree of the LST element that the marker is attached to.
DescriptionThe content of the description of the marker.
Recipe that added the search markerThe specific recipe that added the Search marker.
Source files that errored on a recipe
org.openrewrite.table.SourcesFileErrors

The details of all errors produced by a recipe run.

ColumnDescription
Source pathThe file that failed to parse.
Recipe that made changesThe specific recipe that made a change.
Stack traceThe stack trace of the failure.
Recipe performance
org.openrewrite.table.RecipeRunStats

Statistics used in analyzing the performance of recipes.

ColumnDescription
The recipeThe recipe whose stats are being measured both individually and cumulatively.
Source file countThe number of source files the recipe ran over.
Source file changed countThe number of source files which were changed in the recipe run. Includes files created, deleted, and edited.
Cumulative scanning time (ns)The total time spent across the scanning phase of this recipe.
Max scanning time (ns)The max time scanning any one source file.
Cumulative edit time (ns)The total time spent across the editing phase of this recipe.
Max edit time (ns)The max time editing any one source file.