summaryrefslogtreecommitdiff
path: root/data/removals/15_0/15-0-Retire-js-analyzer.yml
diff options
context:
space:
mode:
Diffstat (limited to 'data/removals/15_0/15-0-Retire-js-analyzer.yml')
-rw-r--r--data/removals/15_0/15-0-Retire-js-analyzer.yml13
1 files changed, 13 insertions, 0 deletions
diff --git a/data/removals/15_0/15-0-Retire-js-analyzer.yml b/data/removals/15_0/15-0-Retire-js-analyzer.yml
new file mode 100644
index 00000000000..5b5d38d039c
--- /dev/null
+++ b/data/removals/15_0/15-0-Retire-js-analyzer.yml
@@ -0,0 +1,13 @@
+- name: "Retire-JS Dependency Scanning tool"
+ announcement_milestone: "14.8"
+ announcement_date: "2022-02-22"
+ removal_milestone: "15.0"
+ removal_date: "2022-05-22"
+ breaking_change: true
+ reporter: sam.white
+ body: | # Do not modify this line, instead modify the lines below.
+ We have removed support for retire.js from Dependency Scanning as of May 22, 2022 in GitLab 15.0. JavaScript scanning functionality will not be affected as it is still being covered by Gemnasium.
+
+ If you have explicitly excluded retire.js using the `DS_EXCLUDED_ANALYZERS` variable, then you will be able to remove the reference to retire.js. If you have customized your pipeline’s Dependency Scanning configuration related to the `retire-js-dependency_scanning` job, then you will want to switch to `gemnasium-dependency_scanning`. If you have not used the `DS_EXCLUDED_ANALYZERS` to reference retire.js, or customized your template specifically for retire.js, you will not need to take any action.
+ stage: secure
+ issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/289830"