.stackat.yml / option

up_to_date

When the dashboard and the weekly digest count a tool as up to date. By default only on its latest release; releases_behind allows some lag.

What it does#

With releases_behind: 1, a tool one stable release behind its latest still counts as up to date; with 2, two; up to 20.

Releases are counted as in the dashboard's Inventory ("Releases behind"): the stable releases after the pinned version, up to the latest. A tool Stackat has no upgrade for (yet) counts as 0 behind.

It changes:

• the dashboard's Up to date card ("13 more than 1 release behind (your setting)") and its trend;
• the weekly digest's Up to date line ("46 of 51 tools within 1 release of the latest (90%, your setting)").

It does not change which issues are opened: a tool one release behind still gets its issue.

When you change it, the whole trend is recounted with the new value, so the weeks stay comparable. Where repositories of one organisation have different values, each is counted with its own and the card says "your settings".

Type and values#

Organisation and repository#

The repository's value replaces the organisation's. The dashboard's Settings tab says where the value in use came from: the default, the organisation's file or the repository's.

Problems you may see#

.stackat.yml: up_to_date.releases_behind must be a whole number from 0 to 20, not 25
.stackat.yml: up_to_date must be a mapping (releases_behind)
.stackat.yml: up_to_date.behind: not a setting (releases_behind)

A bad value leaves the setting as it was: the organisation's, or the default. An up_to_date: key with every line under it commented out is not set.

Examples#

One release of slack, organisation-wide#

up_to_date:
  releases_behind: 1

A repository that upgrades once a year#

up_to_date:
  releases_behind: 3

Strict: only the latest release counts#

The default, written out, for a repository whose organisation allows more.

up_to_date:
  releases_behind: 0