Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit21aae2c

Browse files
Adds notice for Nuget ecosystem and other misc corrections (#39128)
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent11be799 commit21aae2c

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

‎content/code-security/dependabot/working-with-dependabot/dependabot-options-reference.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -750,27 +750,29 @@ The `url` parameter defines where to access a registry. When the optional `repla
750750

751751
## `cooldown` {% octicon "versions" aria-label="cooldown" height="24" %}
752752

753-
Defines a **cooldown period** for dependency updates to delay updates for a configurable number of days. This feature enablesdependabot users to customize how often they receive new version updates, offering greater control over update frequency.
753+
Defines a **cooldown period** for dependency updates to delay updates for a configurable number of days. This feature enables{% data variables.product.prodname_dependabot %} users to customize how often they receive new version updates, offering greater control over update frequency.
754754

755755
> [!NOTE]
756756
> Cooldown is not applicable for security updates.
757+
>
758+
> Cooldown is not available for the **NuGet** ecosystem
757759

758760
### **How Cooldown Works**
759761

760-
* WhenDependabot runs updates as per defined schedule, it checks the **cooldown settings** to determine if new release for dependency is still within its cooldown period.
762+
* When{% data variables.product.prodname_dependabot %} runs updates as per defined schedule, it checks the **cooldown settings** to determine if new release for dependency is still within its cooldown period.
761763
* If new version release date is within the cooldown period, dependency version update is **filtered out** and will not be updated until the cooldown period expires.
762764
* Once the cooldown period ends for new version, the dependency update proceeds based on the standard update strategy defined in `dependabot.yml`.
763765

764-
Without **`cooldown`** (default behaviour):{% data variables.product.prodname_dependabot %}
766+
Without **`cooldown`** (default behaviour):
765767

766768
* Dependabot checks for updates according to the scheduled defined via `schedule.interval`.
767769
* All new versions are considered for updates **immediately**.
768770

769771
With **`cooldown`** enabled:
770772

771-
*Dependabot checks for updates based on the defined `schedule.interval` settings.
773+
*{% data variables.product.prodname_dependabot %} checks for updates based on the defined `schedule.interval` settings.
772774
* **Releases within the cooldown period are ignored.**
773-
*Dependabot updates the dependency to the latest available version **that are no longer in cooldown period** following the configured `versioning-strategy`.
775+
*{% data variables.product.prodname_dependabot %} updates the dependency to the latest available version **that are no longer in cooldown period** following the configured `versioning-strategy`.
774776

775777
### **Cooldown Configuration**
776778

@@ -824,7 +826,6 @@ With **`cooldown`** enabled:
824826
### **Example `dependabot.yml` with cooldown**
825827

826828
```yaml copy
827-
828829
version: 2
829830
updates:
830831
- package-ecosystem: "pip"

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp