LIBSCHOLAR-63 Update .bundler-audit.yml file to current vulnerabilities#1194
Open
Janell-Huyck wants to merge 1 commit intodevelopfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update bundler-audit ignore list for current vulnerabilities
Summary
Updates
.bundler-audit.ymlso the current bundler-audit findings are explicitly ignored, allowing PRs to merge while the team plans gem upgrades.Changes
actionmailer,activesupport,aws-sdk-s3,carrierwave,devise,globalid,httparty,jquery-ui-rails,puma,sidekiq,thor.actionpack,actionview,activerecord,activestorage,loofah,nokogiri,omniauth,rack,rails-html-sanitizer,rexml,webrick.fix: >= 1.4.4) so future upgrades are easier to plan.Notes
This is a temporary measure so CI (and PRs) can pass; the comments in the file document the versions needed to actually fix each finding.
Addressing these will require upgrading gems (notably Rails and related stack) to the versions noted in the comments; that should be tracked and done in a follow-up.
Bjorg has been notified of this action.
Related