From 6ed4ec3e0b1340f96b7c043ef51d1b33bbe85fde Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Mon, 19 Sep 2022 23:18:09 +0000 Subject: Add latest changes from gitlab-org/gitlab@15-4-stable-ee --- ...5-0-remove-background-upload-object-storage.yml | 5 ++-- .../15_3/15-3-vulnerability-report-state-sort.yml | 25 ++++++++++++++++++ .../15_3/15-3-vulnerability-report-tool-sort.yml | 26 +++++++++++++++++++ data/removals/15_3/removal_debian9.yml | 6 +++++ .../15_4/15-4-sast-analyzer-consolidation.yml | 30 ++++++++++++++++++++++ data/removals/templates/example.yml | 2 -- 6 files changed, 89 insertions(+), 5 deletions(-) create mode 100644 data/removals/15_3/15-3-vulnerability-report-state-sort.yml create mode 100644 data/removals/15_3/15-3-vulnerability-report-tool-sort.yml create mode 100644 data/removals/15_3/removal_debian9.yml create mode 100644 data/removals/15_4/15-4-sast-analyzer-consolidation.yml (limited to 'data/removals') diff --git a/data/removals/15_0/15-0-remove-background-upload-object-storage.yml b/data/removals/15_0/15-0-remove-background-upload-object-storage.yml index 16aab3d14c2..dac96032359 100644 --- a/data/removals/15_0/15-0-remove-background-upload-object-storage.yml +++ b/data/removals/15_0/15-0-remove-background-upload-object-storage.yml @@ -43,9 +43,8 @@ gitlab_rails['env'] = { 'GITLAB_LEGACY_BACKGROUND_UPLOADS' => 'artifacts,external_diffs,lfs,uploads,packages,dependency_proxy,terraform_state,pages' } ``` - Prefixes will be supported officially in [GitLab 15.2](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/91307). - This workaround will be dropped, so we encourage migrating to consolidated object storage. - + Support for prefixes was restored in GitLab 15.2 via [this MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/91307). + Support for setting `GITLAB_LEGACY_BACKGROUND_UPLOADS` will be removed in GitLab 15.4. stage: Enablement tiers: [Core, Premium, Ultimate] diff --git a/data/removals/15_3/15-3-vulnerability-report-state-sort.yml b/data/removals/15_3/15-3-vulnerability-report-state-sort.yml new file mode 100644 index 00000000000..3ba5b451718 --- /dev/null +++ b/data/removals/15_3/15-3-vulnerability-report-state-sort.yml @@ -0,0 +1,25 @@ +# +# REQUIRED FIELDS +# +- name: "Vulnerability Report sort by State" # (required) the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. + announcement_milestone: "15.0" # (required) The milestone when this feature was deprecated. + announcement_date: "2022-05-22" # (required) The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. + removal_milestone: "15.3" # (required) The milestone when this feature is being removed. + removal_date: "2022-08-22" # (required) This should almost always be the 22nd of a month (YYYY-MM-DD), the date of the milestone release when this feature will be removed. + breaking_change: false # (required) Change to true if this removal is a breaking change. + reporter: matt_wilson # (required) GitLab username of the person reporting the removal + stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/360516 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + The ability to sort the Vulnerability Report by the `State` column was disabled and put behind a feature flag in GitLab 14.10 due to a refactor + of the underlying data model. The feature flag has remained off by default as further refactoring will be required to ensure sorting + by this value remains performant. Due to very low usage of the `State` column for sorting, the feature flag is instead removed in 15.3 to simplify the codebase and prevent any unwanted performance degradation. +# +# OPTIONAL FIELDS +# + end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end. + end_of_support_date: # (optional) The date of the milestone release when support for this feature will end. + tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] + documentation_url: # (optional) This is a link to the current documentation page + image_url: # (optional) This is a link to a thumbnail image depicting the feature + video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg diff --git a/data/removals/15_3/15-3-vulnerability-report-tool-sort.yml b/data/removals/15_3/15-3-vulnerability-report-tool-sort.yml new file mode 100644 index 00000000000..9aba5ca5ee7 --- /dev/null +++ b/data/removals/15_3/15-3-vulnerability-report-tool-sort.yml @@ -0,0 +1,26 @@ +# +# REQUIRED FIELDS +# +- name: "Vulnerability Report sort by Tool" # (required) the name of the feature being removed. Avoid the words `deprecation`, `deprecate`, `removal`, and `remove` in this field because these are implied. + announcement_milestone: "15.1" # (required) The milestone when this feature was deprecated. + announcement_date: "2022-06-22" # (required) The date of the milestone release when this feature was deprecated. This should almost always be the 22nd of a month (YYYY-MM-DD), unless you did an out of band blog post. + removal_milestone: "15.3" # (required) The milestone when this feature is being removed. + removal_date: "2022-08-22" # (required) This should almost always be the 22nd of a month (YYYY-MM-DD), the date of the milestone release when this feature will be removed. + breaking_change: false # (required) Change to true if this removal is a breaking change. + reporter: matt_wilson # (required) GitLab username of the person reporting the removal + stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/363138 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + The ability to sort the Vulnerability Report by the `Tool` column (scan type) was disabled and put behind a feature flag in GitLab 14.10 due to a refactor + of the underlying data model. The feature flag has remained off by default as further refactoring will be required to ensure sorting + by this value remains performant. Due to very low usage of the `Tool` column for sorting, the feature flag is instead removed in + GitLab 15.3 to simplify the codebase and prevent any unwanted performance degradation. +# +# OPTIONAL FIELDS +# + end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end. + end_of_support_date: # (optional) The date of the milestone release when support for this feature will end. + tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] + documentation_url: # (optional) This is a link to the current documentation page + image_url: # (optional) This is a link to a thumbnail image depicting the feature + video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg diff --git a/data/removals/15_3/removal_debian9.yml b/data/removals/15_3/removal_debian9.yml new file mode 100644 index 00000000000..5438922173f --- /dev/null +++ b/data/removals/15_3/removal_debian9.yml @@ -0,0 +1,6 @@ +- name: "Support for Debian 9" + removal_date: Aug 22, 2022 # day the removal was released + removal_milestone: "15.3" + reporter: dorrino # GitLab username of the person reporting the removal + body: | + Long term service and support (LTSS) for [Debian 9 Stretch ended in July 2022](https://wiki.debian.org/LTS). Therefore, we will no longer support the Debian 9 distribution for the GitLab package. Users can upgrade to Debian 10 or Debian 11. diff --git a/data/removals/15_4/15-4-sast-analyzer-consolidation.yml b/data/removals/15_4/15-4-sast-analyzer-consolidation.yml new file mode 100644 index 00000000000..825fb2b4bfc --- /dev/null +++ b/data/removals/15_4/15-4-sast-analyzer-consolidation.yml @@ -0,0 +1,30 @@ +- name: "SAST analyzer consolidation and CI/CD template changes" + announcement_milestone: "14.8" + announcement_date: "2022-02-22" + removal_milestone: "15.4" + removal_date: "2022-09-22" + breaking_change: true + reporter: connorgilbert + stage: Secure + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/352554 + body: | # (required) Do not modify this line, instead modify the lines below. + We have replaced the GitLab SAST [analyzers](https://docs.gitlab.com/ee/user/application_security/sast/analyzers/) for certain languages in GitLab 15.4 as part of our long-term strategy to deliver a more consistent user experience, faster scan times, and reduced CI minute usage. + + Starting from GitLab 15.4, the [GitLab-managed SAST CI/CD template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml) uses [Semgrep-based scanning](https://docs.gitlab.com/ee/user/application_security/sast/analyzers.html#transition-to-semgrep-based-scanning) instead of the following analyzers: + + - [ESLint](https://gitlab.com/gitlab-org/security-products/analyzers/eslint) for JavaScript, TypeScript, React + - [Gosec](https://gitlab.com/gitlab-org/security-products/analyzers/gosec) for Go + - [Bandit](https://gitlab.com/gitlab-org/security-products/analyzers/bandit) for Python + - [SpotBugs](https://gitlab.com/gitlab-org/security-products/analyzers/spotbugs) for Java + + We will no longer make any updates to the ESLint-, Gosec-, and Bandit-based analyzers. + The SpotBugs-based analyzer will continue to be used for Groovy, Kotlin, and Scala scanning. + + We won't delete container images previously published for these analyzers, so older versions of the CI/CD template will continue to work. + + If you changed the default GitLab SAST configuration, you may need to update your configuration as detailed in the [deprecation issue for this change](https://gitlab.com/gitlab-org/gitlab/-/issues/352554#actions-required). +# The following items are not published on the docs page, but may be used in the future. + tiers: [Free, Silver, Gold, Core, Premium, Ultimate] + documentation_url: https://docs.gitlab.com/ee/user/application_security/sast/analyzers.html#transition-to-semgrep-based-scanning # (optional) This is a link to the current documentation page + image_url: # (optional) This is a link to a thumbnail image depicting the feature + video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg diff --git a/data/removals/templates/example.yml b/data/removals/templates/example.yml index 3674583cd7d..8d7d694be26 100644 --- a/data/removals/templates/example.yml +++ b/data/removals/templates/example.yml @@ -32,8 +32,6 @@ # # OPTIONAL FIELDS # - end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - end_of_support_date: # (optional) The date of the milestone release when support for this feature will end. tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] documentation_url: # (optional) This is a link to the current documentation page image_url: # (optional) This is a link to a thumbnail image depicting the feature -- cgit v1.2.3