Clear remaining bundle-audit findings (Rails 8.1.3.1 + transitive bumps) - #153
Merged
Conversation
bundle update rails nokogiri json loofah net-imap crass concurrent-ruby rails-html-sanitizer, clearing every bundle-audit finding disclosed since PR #150 last ran CI. Rails itself moves 8.1.3 -> 8.1.3.1; the rest are indirect dependencies pulled in by it. Only affects the dev/CI sandbox (Gemfile.lock) — none of these are gemspec runtime dependencies of the published gem.
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
bundle update rails nokogiri json loofah net-imap crass concurrent-ruby rails-html-sanitizerbundle-auditfinding disclosed since PR Bump simplecov from 0.22.0 to 1.0.3 #150 last ran CI on 2026-07-30:activestorage(via Rails 8.1.3 → 8.1.3.1),nokogiri1.19.3 → 1.19.4,loofah2.25.1 → 2.25.2,net-imap0.6.4 → 0.6.6,crass1.0.6 → 1.0.7,concurrent-ruby1.3.6 → 1.3.8,rails-html-sanitizer1.7.0 → 1.7.1jsonwas already at 2.21.2 (newer than the fix version) via a transitive resolution, so bundler left it alonerails— none are gemspec runtime dependencies of the published gem, so this only affects the dev/CI sandbox, not gem consumersTest plan
bundle exec bundle-audit check— no vulnerabilities foundbundle exec rake(bundle-audit + rubocop + zeitwerk + rspec) — exits 0, 363 examples / 0 failures, 100% coverage