Skip to content
Snippets Groups Projects
Commit 96b3bd61 authored by John Skarbek's avatar John Skarbek
Browse files

Merge branch 'enablement-deprecations-patch-1' into '14-9-stable-ee-patch-1'

Add deprecation notices that missed the 14.9.0 release tag

See merge request gitlab-org/gitlab!83451
parents c615d177 9fbd0a9a
No related branches found
No related tags found
No related merge requests found
- name: "Background upload for object storage"
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.
To reduce the overall complexity and maintenance burden of GitLab's [object storage feature](https://docs.gitlab.com/ee/administration/object_storage.html), support for using `background_upload` to upload files is deprecated and will be fully removed in GitLab 15.0.
This impacts a small subset of object storage providers:
- **OpenStack** Customers using OpenStack need to change their configuration to use the S3 API instead of Swift.
- **RackSpace** Customers using RackSpace-based object storage need to migrate data to a different provider.
GitLab will publish additional guidance to assist affected customers in migrating.
stage: Enablement
tiers: [Core, Premium, Ultimate]
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/26600
documentation_url: https://docs.gitlab.com/ee/administration/object_storage.html
- name: "Deprecate support for Debian 9"
announcement_milestone: "14.9"
announcement_date: "2022-03-22"
removal_milestone: "15.1"
removal_date: "2022-06-22"
body: |
Long term service and support (LTSS) for [Debian 9 Stretch ends in July 2022](https://wiki.debian.org/LTS). Therefore, we will longer support the Debian 9 distribution for the GitLab package. Users can upgrade to Debian 10 or Debian 11.
- 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.
- 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.
Loading
Loading
@@ -38,6 +38,31 @@ For deprecation reviewers (Technical Writers only):
 
## 14.9
 
### Background upload for object storage
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.
To reduce the overall complexity and maintenance burden of GitLab's [object storage feature](https://docs.gitlab.com/ee/administration/object_storage.html), support for using `background_upload` to upload files is deprecated and will be fully removed in GitLab 15.0.
This impacts a small subset of object storage providers:
- **OpenStack** Customers using OpenStack need to change their configuration to use the S3 API instead of Swift.
- **RackSpace** Customers using RackSpace-based object storage need to migrate data to a different provider.
GitLab will publish additional guidance to assist affected customers in migrating.
**Planned removal milestone: 15.0 (2022-05-22)**
### Deprecate support for Debian 9
Long term service and support (LTSS) for [Debian 9 Stretch ends in July 2022](https://wiki.debian.org/LTS). Therefore, we will longer support the Debian 9 distribution for the GitLab package. Users can upgrade to Debian 10 or Debian 11.
**Planned removal milestone: 15.1 (2022-06-22)**
### GitLab Pages running as daemon
 
In 15.0, support for daemon mode for GitLab Pages will be removed.
Loading
Loading
@@ -109,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`
Loading
Loading
Loading
Loading
@@ -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
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment