diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-04-24 12:09:43 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-04-24 12:09:43 +0300 |
| commit | 028c7bdc315c3770f2ccc86f1100d90a5f702cad (patch) | |
| tree | ee46807784d115a6bc4ffedbbd94588025e80b01 /doc/api | |
| parent | d1727df7469dacdf782140d69e5cf3aa08d75ec9 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/api')
| -rw-r--r-- | doc/api/rest/deprecations.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/api/rest/deprecations.md b/doc/api/rest/deprecations.md index 7bfc9e1f59e..0299a2c4a73 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). |