Commit eb9b0e87 authored by Adam Hegyi's avatar Adam Hegyi Committed by Marcin Sedlak-Jakubowski

Deprecation entry for instance_statistics_measurements

This change adds deprecation entry for the
instance_statistics_measurements GraphQL node.
parent d85203ce
- name: "Querying Usage Trends via the `instanceStatisticsMeasurements` GraphQL node"
announcement_milestone: "14.8"
announcement_date: "2022-02-22"
removal_milestone: "15.0"
removal_date: "2022-05-22"
breaking_change: true
body: | # Do not modify this line, instead modify the lines below.
The `instanceStatisticsMeasurements` GraphQL node has been renamed to `usageTrendsMeasurements` in 13.10 and the old field name has been marked as deprecated. To fix the existing GraphQL queries, replace `instanceStatisticsMeasurements` with `usageTrendsMeasurements`.
# The following items are not published on the docs page, but may be used in the future.
stage: Manage
tiers: [FREE]
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/332323
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/index.html#queryusagetrendsmeasurements
......@@ -717,6 +717,18 @@ The `merged_by` field in the [merge request API](https://docs.gitlab.com/ee/api/
## 14.8
### Querying Usage Trends via the `instanceStatisticsMeasurements` GraphQL node
WARNING:
This feature will be changed or removed in 15.0
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
changes to your code, settings, or workflow.
The `instanceStatisticsMeasurements` GraphQL node has been renamed to `usageTrendsMeasurements` in 13.10 and the old field name has been marked as deprecated. To fix the existing GraphQL queries, replace `instanceStatisticsMeasurements` with `usageTrendsMeasurements`.
**Planned removal milestone: 15.0 (2022-05-22)**
### REST and GraphQL API Runner usage of `active` replaced by `paused`
WARNING:
......
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