Add bundle-audit to CI for Gemfile.lock CVE gating#5
Merged
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
1 participant
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.
Summary
bundler-auditto thegroup :developmentdev gems.auditjob in.github/workflows/ci.ymlrunsbundle exec bundle-audit check --updateon every push and PR, gating merges on any known CVE inGemfile.lock.rake audittask available locally (not inrake default— keeps the common dev loop fast and offline-capable).[Unreleased].Complements the Dependabot config landed in PR #4: Dependabot keeps
Gemfile.lockmoving as new gem versions drop;bundle-auditenforces "can't merge with a known CVE in the current lockfile."Test plan
bundle exec rake auditpasses locally (1078 advisories; no vulnerabilities found).bundle exec rake(spec + rubocop) still green — 226 examples, no offenses.auditjob turns green on the PR.