diff --git a/data/deprecations/15-8-default-private-user-profile.yml b/data/deprecations/15-8-default-private-user-profile.yml deleted file mode 100644 index d07163e1ca99b43a99f6f6c7efa8a69c22d264bb..0000000000000000000000000000000000000000 --- a/data/deprecations/15-8-default-private-user-profile.yml +++ /dev/null @@ -1,9 +0,0 @@ -- title: "Null value for `private_profile` attribute in User API is deprecated" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters." - announcement_milestone: "15.8" # (required) The milestone when this feature was first announced as deprecated. - removal_milestone: "16.0" # (required) The milestone when this feature is planned to be removed - breaking_change: true # (required) Change to false if this is not a breaking change. - reporter: lohrc # (required) GitLab username of the person reporting the change - stage: manage # (required) String value of the stage that the feature was created in. e.g., Growth - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/387005 # (required) Link to the deprecation issue in GitLab - body: | # (required) Do not modify this line, instead modify the lines below. - When creating and updating users through the API, `null` was a valid value for the `private_profile` attribute, which would internally be converted to the default value. Starting with 16.0, `null` will no longer be a valid value for this parameter, and the response will be a 400 if used. Now the only valid values are `true` and `false`. diff --git a/doc/api/rest/deprecations.md b/doc/api/rest/deprecations.md index 7bfc9e1f59ecc79477fb13f2e853105c257eba61..0299a2c4a7340543543a121f96a94e465517c219 100644 --- a/doc/api/rest/deprecations.md +++ b/doc/api/rest/deprecations.md @@ -31,6 +31,12 @@ has been deprecated in favor of the `detailed_merge_status` field which more cor all of the potential statuses that a merge request can be in. API users are encouraged to use the new `detailed_merge_status` field instead. The `merge_status` field will be removed in v5 of the GitLab REST API. +### Null value for `private_profile` attribute in User API + +Breaking change. [Related issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387005). + +When creating and updating users through the API, `null` was a valid value for the `private_profile` attribute, which would internally be converted to the default value. In v5 of the GitLab REST API, `null` will no longer be a valid value for this parameter, and the response will be a 400 if used. After this change, the only valid values will be `true` and `false`. + ## Single merge request changes API endpoint Breaking change. [Related issue](https://gitlab.com/gitlab-org/gitlab/-/issues/322117). diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md index 1ebfff9acc57a031d5ac5795fcf51e46d972076f..53d1d356a77957b10762a2ac31077cdf843ff572 100644 --- a/doc/update/deprecations.md +++ b/doc/update/deprecations.md @@ -1376,19 +1376,6 @@ and `config/redis.shared_state.yml` files. <div class="deprecation breaking-change" data-milestone="16.0"> -### Null value for `private_profile` attribute in User API is deprecated - -<div class="deprecation-notes"> -- Announced in: GitLab <span class="milestone">15.8</span> -- [Breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/) -</div> - -When creating and updating users through the API, `null` was a valid value for the `private_profile` attribute, which would internally be converted to the default value. Starting with 16.0, `null` will no longer be a valid value for this parameter, and the response will be a 400 if used. Now the only valid values are `true` and `false`. - -</div> - -<div class="deprecation breaking-change" data-milestone="16.0"> - ### Old versions of JSON web tokens are deprecated <div class="deprecation-notes">