fleetlint Policy for a fleet of repositories
v0.9
Getting started

deps/update-cooldown

Fresh releases wait before they are proposed

Severityinfo
Tiers1, 2
Stacksany
Scoperoot
Kindexpr
Sourcelibrary v0.6.0
Selected byfleetlint-recommended@v0.6.0

Requirement

Update automation waits a few days before proposing a new release: Renovate’s minimumReleaseAge (or the older stabilityDays) is set, or every Dependabot updates entry has a cooldown.

Why

Hijacked releases are usually found and pulled within days; a short wait keeps them out of the lockfile.

Applies when

params.renovate.exists(f, file(f)) || file(".github/dependabot.yml") || file(".github/dependabot.yaml")

Check

params.renovate.exists(f, file(f) && text(f).matches(r'["\x27]?(minimumReleaseAge|stabilityDays)["\x27]?\s*:')) || ["dependabot.yml", "dependabot.yaml"].exists(n, file(".github/" + n)
  && yaml(".github/" + n) != null && "updates" in yaml(".github/" + n) && yaml(".github/" + n).updates.size() > 0
  && yaml(".github/" + n).updates.all(u, "cooldown" in u))

Parameters

  • renovate: [renovate.json renovate.json5 .renovaterc .renovaterc.json .renovaterc.json5 .github/renovate.json .github/renovate.json5 .gitea/renovate.json .gitea/renovate.json5 .forgejo/renovate.json .forgejo/renovate.json5 .gitlab/renovate.json .gitlab/renovate.json5]

Fix

Set "minimumReleaseAge": "3 days" in renovate.json, or cooldown: {default-days: 3} on each Dependabot entry.

Agent instruction: Add minimumReleaseAge (Renovate) or a cooldown per updates entry (Dependabot) of a few days; keep security updates immediate where the tool allows it.

A finding of this rule points at the file (params.renovate.filter(f, file(f)) + [".github/dependabot.yml", ".github/dependabot.yaml"].filter(f, file(f)) + [".github/dependabot.yml"])[0] yields.

Sources


Generated by fleetlint docs from catalog v0.6.0.