.stackat.yml / option

cooldown

How long a release must be out before Stackat proposes it. Like Renovate's minimumReleaseAge or Dependabot's cooldown.

What it does#

With cooldown: 14, an issue or pull request targets the newest release that has been out at least 14 days, not simply the latest one.

• The issue lists the releases held back and the day each becomes eligible.
• A tool whose newer releases are all still cooling gets no new issue, and its open issue stays open.
• Stackat still reads every release on the day it comes out, so the analysis is ready the day the cooldown ends.
• A critical security patch skips the cooldown unless you set critical_skips_cooldown: false.

Type and values#

Weeks count as 7 days. Case and spaces do not matter ("2W", "14 d").

Organisation and repository#

Set it once in the organisation's file for every repository. A repository's own cooldown replaces it; cooldown: 0 turns it off for that repository.

Problems you may see#

.stackat.yml: cooldown must be between 0 and 365 days, not 400
.stackat.yml: cooldown 'two weeks' is not a number of days (14, "14d" or "2w")
.stackat.yml: cooldown is a number of days, not true/false

The message says cooldown whichever of the three names you used. A bad value is ignored, and the organisation's value, or no cooldown, applies.

Examples#

Two weeks, organisation-wide#

cooldown: 2w

A longer wait for one regulated repository#

cooldown: 30            # change control: a month in the wild first
critical_skips_cooldown: true

No cooldown for a sandbox, whatever the organisation says#

cooldown: 0