Commit 4ca5fddd authored by John McGuire's avatar John McGuire Committed by Russell Dickenson

Rate limit user_email_lookup_limit removal

parent 6d7f66dc
- 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.
......@@ -42,6 +42,16 @@ 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
......
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