From ad1d314270819ce6e9b100215b4011e4b3ae41f6 Mon Sep 17 00:00:00 2001 From: Hannah Sutor <hsutor@gitlab.com> Date: Wed, 10 Aug 2022 01:19:16 +0000 Subject: [PATCH] Add ommniauth crowd deprecation post --- data/deprecations/15-3-omniauth-crowd.yml | 16 ++++++++++++++++ doc/update/deprecations.md | 16 ++++++++++++++++ 2 files changed, 32 insertions(+) create mode 100644 data/deprecations/15-3-omniauth-crowd.yml diff --git a/data/deprecations/15-3-omniauth-crowd.yml b/data/deprecations/15-3-omniauth-crowd.yml new file mode 100644 index 0000000000000..59f99083b280b --- /dev/null +++ b/data/deprecations/15-3-omniauth-crowd.yml @@ -0,0 +1,16 @@ +# +# REQUIRED FIELDS +# +- name: "`omniauth_crowd` gem" # (required) The name of the feature to be deprecated + announcement_milestone: "15.3" # (required) The milestone when this feature was first announced as deprecated. + announcement_date: "2022-08-22" # (required) The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "16.0" # (required) The milestone when this feature is planned to be removed + removal_date: "2023-05-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # (required) If this deprecation is a breaking change, set this value to true + reporter: hsutor # (required) GitLab username of the person reporting the deprecation + 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/369117 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + The `omniauth_crowd` gem will be removed in our next major release, GitLab 16.0. This gem sees very little use and + its [lack of compatability](https://github.com/robdimarco/omniauth_crowd/issues/37) with OmniAuth 2.0 is blocking + our upgrade. diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md index 79e54e0bf7c12..a5f4ef646ae82 100644 --- a/doc/update/deprecations.md +++ b/doc/update/deprecations.md @@ -73,6 +73,22 @@ Review the details carefully before upgrading. The `omniauth-cas3` gem will be removed in our next major release, GitLab 16.0. This gem sees very little use and its lack of upstream maintence is preventing GitLab's [upgrade to OmniAuth 2.0](https://gitlab.com/gitlab-org/gitlab/-/issues/30073). +</div> + +<div class="deprecation removal-160 breaking-change"> + +### `omniauth_crowd` gem + +Planned removal: GitLab <span class="removal-milestone">16.0</span> (2023-05-22) + +WARNING: +This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +Review the details carefully before upgrading. + +The `omniauth_crowd` gem will be removed in our next major release, GitLab 16.0. This gem sees very little use and +its [lack of compatability](https://github.com/robdimarco/omniauth_crowd/issues/37) with OmniAuth 2.0 is blocking +our upgrade. + </div> </div> -- GitLab