.stackat.yml / option

critical_skips_cooldown

Whether a critical security patch is proposed straight away, even inside your cooldown.

What it does#

With a cooldown set, an upgrade with a patch urgency of 90 or more, or one that fixes a vulnerability on CISA's list of exploited vulnerabilities, is proposed right away. The issue says why: "This upgrade skips your 14-day cooldown: …".

• true (the default): critical patches skip the cooldown.
• false: the cooldown holds even for them.

Without a cooldown this setting changes nothing.

Type and values#

Organisation and repository#

The repository's value replaces the organisation's.

Problems you may see#

.stackat.yml: critical_skips_cooldown must be true or false

The setting is then ignored, and the organisation's value, or true, applies.

Examples#

The usual: wait, except for critical fixes#

cooldown: 14
critical_skips_cooldown: true

A strict freeze: nothing younger than 30 days#

cooldown: 30
critical_skips_cooldown: false   # even critical patches wait