From 65a878aed2a34e5266b0f239de587da91217566e Mon Sep 17 00:00:00 2001 From: atharvasingh7007 Date: Mon, 13 Apr 2026 21:25:23 +0530 Subject: [PATCH] docs: align dependabot cooldown wording --- .../optimizing-pr-creation-version-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/code-security/tutorials/secure-your-dependencies/optimizing-pr-creation-version-updates.md b/content/code-security/tutorials/secure-your-dependencies/optimizing-pr-creation-version-updates.md index 0f39d0ebba1f..15e74f77cf37 100644 --- a/content/code-security/tutorials/secure-your-dependencies/optimizing-pr-creation-version-updates.md +++ b/content/code-security/tutorials/secure-your-dependencies/optimizing-pr-creation-version-updates.md @@ -60,7 +60,7 @@ See also [schedule](/code-security/dependabot/working-with-dependabot/dependabot ### Setting up a cooldown period for dependency updates -You can use `cooldown` with a combination of options to control when {% data variables.product.prodname_dependabot %} creates pull requests for **version updates**. +You can use `cooldown` with a combination of options to define a **cooldown period** for dependency updates. The `cooldown` option is only available for _version_ updates, not _security_ updates. The example `dependabot.yml` file below shows a cooldown period being applied to the dependencies `requests`, `numpy`, and those prefixed with `pandas` or `django`, but not to the dependency called `pandas` (exact match), which is excluded via the **exclude** list.