@types/node release history

A practical setting

Give a new release three days.

In this snapshot, a 3-day cooldown would have waited past the replacement patch for 20 releases of @types/node fixed within 72 hours. This describes release timing; it does not establish why a patch was published or guarantee that an update will hold up.

Merge these settings into your existing configuration and adjust the manifest directory. Dependabot applies this to version updates; security updates are handled separately. The Dependabot example covers the ecosystem; the Renovate example targets this package.

version: 2
updates:
  - package-ecosystem: "npm"
    directory: "/"
    schedule:
      interval: "daily"
    cooldown:
      default-days: 3

{
  "packageRules": [
    {
      "matchDatasources": [
        "npm"
      ],
      "matchPackageNames": [
        "@types/node"
      ],
      "minimumReleaseAge": "3 days"
    }
  ]
}

Dependabot cooldown reference · Renovate release age reference