debian-mirror-gitlab/data/deprecations/15-0-runner-status-legacy-mode.yml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

19 lines
1.6 KiB
YAML
Raw Normal View History

2022-07-16 23:28:13 +05:30
- name: "GraphQL API legacyMode argument for Runner status" # The name of the feature to be deprecated
announcement_milestone: "15.0" # The milestone when this feature was first announced as deprecated.
announcement_date: "2022-05-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
removal_milestone: "16.0" # The milestone when this feature is planned to be removed
removal_date: "2023-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
breaking_change: true # If this deprecation is a breaking change, set this value to true
reporter: pedropombeiro # GitLab username of the person reporting the deprecation
body: | # Do not modify this line, instead modify the lines below.
The `legacyMode` argument to the `status` field in `RunnerType` will be rendered non-functional in the 16.0 release
as part of the deprecations details in the [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351109).
In GitLab 16.0 and later, the `status` field will act as if `legacyMode` is null. The `legacyMode` argument will
be present during the 16.x cycle to avoid breaking the API signature, and will be removed altogether in the
17.0 release.
stage: Verify
tiers: [Core, Premium, Ultimate]
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/360545
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#cirunnerstatus