Repository navigation
Update loofah, nokogiri and rails-html-sanitizer to clear advisories - #878
Conversation
Conservative relock (loofah 2.25.3, nokogiri 1.19.7, rails-html-sanitizer 1.7.2) that keeps every platform entry already in the lockfile. Gemfile.lock only. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters: 1
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
🚀 Quick Review App CommandsWelcome! Here are the commands you can use in this PR:
|
|
Review: this only bumps |
|
No description provided. |
|
No description provided. |
✅ Review App DeletedReview app for PR #878 is deleted |
Summary
New ruby-advisory-db entries flag the locked
loofah(< 2.25.3),nokogiri(1.19.4) andrails-html-sanitizer(< 1.7.2), which turnsbundler-auditred on any run (seen on TanStack main, not caused by the rc.3 bump). This is a conservative relock:bundle lock --update loofah nokogiri rails-html-sanitizer --conservative.Gemfile.lockis the only changed filerails-html-sanitizerwas added to the requested pair because the same advisory run flags it (>= 1.7.2); Hacker News did the same in its #127.Verification
bundle checkpasses;Nokogiri 1.19.7 / Loofah 2.25.3 / Rails::HTML::Sanitizer 1.7.2load underbundle exec.bundler-audit checkreports no remaining advisories for these three gems. See PR checks for the full CI run.