Added deprecation notice for user_email_lookup_limit

data/deprecations/14-9-global-search-deprecate-user-email-lookup-limit.yml

+- name: "user_email_lookup_limit API field"
+  announcement_milestone: "14.9"
+  announcement_date: "2022-03-22"
+  removal_milestone: "15.0"
+  removal_date: "2022-05-22"
+  breaking_change: true
+  reporter: fzimmer
+  body: |  # Do not modify this line, instead modify the lines below.
+    The `user_email_lookup_limit` [API field](https://docs.gitlab.com/ee/api/settings.html) is deprecated and will be removed in GitLab 15.0. Until GitLab 15.0, `user_email_lookup_limit` is aliased to `search_rate_limit` and existing workflows will continue to work.
+
+    Any API calls attempting to change the rate limits for `user_email_lookup_limit` should use `search_rate_limit` instead.

data/removals/14_9/14-9-key-user_email_lookup_limit.yml

-- name: "Renamed 'user_email_lookup_limit' to 'search_rate_limit' API field"
-  announcement_milestone: "14.9"
-  announcement_date: "2022-03-22"
-  removal_milestone: "14.9"
-  removal_date: "2022-03-22"
-  breaking_change: true
-  reporter: fzimmer
-  body: |
-    We renamed the rate limit key from `user_email_lookup_limit` to `search_rate_limit`. Any API calls attempting to change the rate limits for `user_email_lookup_limit` should use `search_rate_limit` instead.

doc/update/deprecations.md

@@ -134,6 +134,20 @@ Since it isn't used in the context of GitLab (the product), `htpasswd` authentic
 
 **Planned removal milestone: 15.0 (2022-05-22)**
 
+### user_email_lookup_limit API field
+
+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 `user_email_lookup_limit` [API field](https://docs.gitlab.com/ee/api/settings.html) is deprecated and will be removed in GitLab 15.0. Until GitLab 15.0, `user_email_lookup_limit` is aliased to `search_rate_limit` and existing workflows will continue to work.
+
+Any API calls attempting to change the rate limits for `user_email_lookup_limit` should use `search_rate_limit` instead.
+
+**Planned removal milestone: 15.0 (2022-05-22)**
+
 ## 14.8
 
 ### Changes to the `CI_JOB_JWT`

doc/update/removals.md

@@ -42,16 +42,6 @@ In GitLab 14.4, GitLab released an integrated error tracking backend that replac
 
 For additional background on this removal, please reference [Disable Integrated Error Tracking by Default](https://gitlab.com/groups/gitlab-org/-/epics/7580). If you have feedback please add a comment to [Feedback: Removal of Integrated Error Tracking](https://gitlab.com/gitlab-org/gitlab/-/issues/355493).
 
-### Renamed 'user_email_lookup_limit' to 'search_rate_limit' API field
-
-WARNING:
-This feature was changed or removed in 14.9
-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.
-
-We renamed the rate limit key from `user_email_lookup_limit` to `search_rate_limit`. Any API calls attempting to change the rate limits for `user_email_lookup_limit` should use `search_rate_limit` instead.
-
 ## 14.6
 
 ### Limit the number of triggered pipeline to 25K in free tier