diff options
| author | Zeger-Jan van de Weg <git@zjvandeweg.nl> | 2018-09-06 16:02:05 +0300 |
|---|---|---|
| committer | Zeger-Jan van de Weg <git@zjvandeweg.nl> | 2018-09-06 16:02:05 +0300 |
| commit | 9f2bc51496d18e8dd380e8fd9fe2bd9a2b52e592 (patch) | |
| tree | 69dc3640c2325350d62b3ba73700b25b154363a7 | |
| parent | 74f1fb87a47bbb5d65c58a0f419657b4fd4fc039 (diff) | |
Reset sanitize requirements in lockfile
Honestly not quite sure how this number got bumped, but it seems that
the minimum version didn't get bumped but the correct version got used
by bundler.
The report was out of date, as the scanner got removed. However, GitLab
tried to find a pipeline with scanning enabled, and did so from before
it got removed.
So long story short, this was never broken, and while I fixed it I broke
something. I _think_ it has to do with the `--no-deployment` flag.
| -rw-r--r-- | ruby/Gemfile.lock | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ruby/Gemfile.lock b/ruby/Gemfile.lock index 862d278cd..99abf5d97 100644 --- a/ruby/Gemfile.lock +++ b/ruby/Gemfile.lock @@ -33,7 +33,7 @@ GEM gollum-grit_adapter (~> 1.0) nokogiri (>= 1.6.1, < 2.0) rouge (~> 3.1) - sanitize (~> 4.6.6) + sanitize (~> 4.6.4) stringex (~> 2.6) gitlab-gollum-rugged_adapter (0.4.4.1) mime-types (>= 1.15) |