API: OFFLINE and NOT_CONNECTED runner status can be returned as new STALE status
Deprecation Summary
NOTE: Several changes were made to the CiRunnerStatus
GraphQL enum, affecting the nomenclature and situations where certain values are returned. A resolver allowing a legacyMode
argument to be passed to the state
resolver to allow preserving backward compatibility was added. This resolver should be removed in %15.0.
In the REST and GraphQL APIs, a new STALE
value was added in %14.6 which will be returned in place of OFFLINE
and NOT_CONNECTED
Runner status if the runner has not contacted the instance in more than 3 months. This is a broken change for users that are expecting the old values.
Breaking Change
A breaking change will occur in %15.0 even when the legacyMode
argument to the CiRunnerType.status
field is unspecified or set to the default value of "14.5":
- a new
STALE
value was added and will be returned in certain situations which would previously returnOFFLINE
orNOT_CONNECTED
(if the runner has not shown up in the last 3 months);
Affected Topology
Both Self-managed users and SaaS users.
Affected Tier
All tiers.
Checklist
-
@mention your stage's stable counterparts on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager. - To see who the stable counterparts are for a product team visit product categories
- If there is no stable counterpart listed for Sales/CS please mention
@timtams
- If there is no stable counterpart listed for Support please @mention
@gitlab-com/support/managers
- If there is no stable counterpart listed for Marketing please mention
@williamchia
- If there is no stable counterpart listed for Sales/CS please mention
- To see who the stable counterparts are for a product team visit product categories
-
@mention your GPM so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.