Skip to content

Deprecate `DISABLED_WITH_OVERRIDE` in SharedRunnersSetting

For guidance on the overall deprecations, removals and breaking changes workflow, please visit Breaking changes, deprecations, and removing features

Deprecation Summary

The value DISABLED_WITH_OVERRIDE in SharedRunnerSetting is being replaced by the value DISABLED_AND_OVERRIDABLE.

Users should expect to have to handle a new value (disabled_and_overridable) being returned. The old value will no longer be returned.

Breaking Change

The DISABLED_WITH_OVERRIDE value of the SharedRunnersSetting GraphQL enum type will be replaced with the value DISABLED_AND_OVERRIDABLE. DISABLED_WITH_OVERRIDE will no longer be returned and users will need to update their workflow to handle the new value.

Affected Topology

Affected Tier

Checklists

Labels

  • This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
  • This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

Please add links to the relevant merge requests.

!106322 (merged)

  • As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
  • On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post.
  • On the major milestone:

Mentions

  • Your stage's stable counterparts have been @mentioned 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 @cfoster3
  • Your GPM has been @mentioned 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.

Deprecation Milestone

%15.8

Planned Removal Milestone

%17.0

Links

Edited by Pedro Pombeiro