diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-10-31 18:09:25 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-10-31 18:09:25 +0000 |
| commit | 30b8ea126ffffc9bef610d38f8ebcd91bb687aba (patch) | |
| tree | 3705b43015a6d3a1fd85864f1fc555383b8e248b /doc/development/gemfile.md | |
| parent | a5519693560d1ac4e120e1afd7d806d13a2d09fd (diff) | |
| download | gitlab-ce-30b8ea126ffffc9bef610d38f8ebcd91bb687aba.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/gemfile.md')
| -rw-r--r-- | doc/development/gemfile.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/gemfile.md b/doc/development/gemfile.md index 7d3531afb49..3c7dc19da8e 100644 --- a/doc/development/gemfile.md +++ b/doc/development/gemfile.md @@ -66,7 +66,7 @@ This means that new dependencies should, at a minimum, meet the following criter When adding a new gem to our `Gemfile` or even changing versions in `Gemfile.lock` it is strongly recommended that you -[request a Security review](https://about.gitlab.com/handbook/engineering/security/#how-to-request-a-security-review). +[request a Security review](https://about.gitlab.com/handbook/security/#how-to-request-a-security-review). New gems add an extra security risk for GitLab, and it is important to evaluate this risk before we ship this to production. Technically, just adding a new gem and pushing to a branch in our main `gitlab` project is a security |