Commit d973ec3c authored by Suzanne Selhorn's avatar Suzanne Selhorn

Merge branch 'pedropombeiro/343262/move-removal-milestone-to-16.0' into 'master'

Move 'paused' removal milestone to 16.0

See merge request gitlab-org/gitlab!83881
parents f9154aa0 2f11e7b8
- name: "REST and GraphQL API Runner status will not return `paused`" - name: "REST and GraphQL API Runner status will not return `paused`"
announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
announcement_date: "2021-11-22" announcement_date: "2021-11-22"
removal_milestone: "15.0" # the milestone when this feature is planned to be removed removal_milestone: "16.0" # the milestone when this feature is planned to be removed
removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed removal_date: "2023-04-22" # the date of the milestone release when this feature is planned to be removed
breaking_change: true breaking_change: true
body: | # Do not modify this line, instead modify the lines below. body: | # Do not modify this line, instead modify the lines below.
The GitLab Runner REST and GraphQL API endpoints will not return `paused` or `active` as a status in GitLab 15.0. The GitLab Runner REST and GraphQL API endpoints will not return `paused` or `active` as a status in GitLab 16.0.
A runner's status will only relate to runner contact status, such as: A runner's status will only relate to runner contact status, such as:
`online`, `offline`, or `not_connected`. Status `paused` or `active` will no longer appear. `online`, `offline`, or `not_connected`. Status `paused` or `active` will no longer appear.
......
...@@ -1315,12 +1315,12 @@ In milestone 15.0, we will remove the `pipelines` attribute from the API respons ...@@ -1315,12 +1315,12 @@ In milestone 15.0, we will remove the `pipelines` attribute from the API respons
### REST and GraphQL API Runner status will not return `paused` ### REST and GraphQL API Runner status will not return `paused`
WARNING: WARNING:
This feature will be changed or removed in 15.0 This feature will be changed or removed in 16.0
as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes). as a [breaking change](https://docs.gitlab.com/ee/development/contributing/#breaking-changes).
Before updating GitLab, review the details carefully to determine if you need to make any Before updating GitLab, review the details carefully to determine if you need to make any
changes to your code, settings, or workflow. changes to your code, settings, or workflow.
The GitLab Runner REST and GraphQL API endpoints will not return `paused` or `active` as a status in GitLab 15.0. The GitLab Runner REST and GraphQL API endpoints will not return `paused` or `active` as a status in GitLab 16.0.
A runner's status will only relate to runner contact status, such as: A runner's status will only relate to runner contact status, such as:
`online`, `offline`, or `not_connected`. Status `paused` or `active` will no longer appear. `online`, `offline`, or `not_connected`. Status `paused` or `active` will no longer appear.
...@@ -1328,7 +1328,7 @@ A runner's status will only relate to runner contact status, such as: ...@@ -1328,7 +1328,7 @@ A runner's status will only relate to runner contact status, such as:
When checking if a runner is `paused`, API users are advised to check the boolean attribute When checking if a runner is `paused`, API users are advised to check the boolean attribute
`paused` to be `true` instead. When checking if a runner is `active`, check if `paused` is `false`. `paused` to be `true` instead. When checking if a runner is `active`, check if `paused` is `false`.
**Planned removal milestone: 15.0 (2022-05-22)** **Planned removal milestone: 16.0 (2023-04-22)**
### Support for SLES 12 SP2 ### Support for SLES 12 SP2
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment