build(deps): bump nokogiri from 1.15.3 to 1.19.4 in /docs/multiple-tests/multi-patterns/src#220
Conversation
Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.15.3 to 1.19.4. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md) - [Commits](sparklemotion/nokogiri@v1.15.3...v1.19.4) --- updated-dependencies: - dependency-name: nokogiri dependency-version: 1.19.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 0 |
AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes.
There was a problem hiding this comment.
Pull Request Overview
The PR updates nokogiri to version 1.19.4 to address several security vulnerabilities. While the change itself is positive and the PR is marked as up to standards by automated analysis, there are significant security risks and compatibility considerations that should be addressed.
Specifically, the Gemfile.lock reveals that the project continues to use highly vulnerable versions of rack and activesupport. Furthermore, the upgrade to Nokogiri 1.19.0+ drops support for Ruby 3.1 and JRuby 9.4, which may impact the project's runtime environment.
About this PR
- Nokogiri 1.19.0 and later versions have dropped support for Ruby 3.1 and JRuby 9.4. Please verify that the project's runtime environment and CI/CD pipelines are using a supported Ruby version (>= 3.2) before merging.
2 comments outside of the diff
docs/multiple-tests/multi-patterns/src/Gemfile.lock
line 44🔴 HIGH RISK
This version ofrackis affected by numerous critical security vulnerabilities, including risks of DoS, XSS, and unauthorized session access. A significant update to the Rack dependency is recommended to secure the application.
line 26🔴 HIGH RISK
Theactivesupportdependency is vulnerable to a high-severity Denial of Service attack (CVE-2026-33176). It is recommended to upgrade the Rails framework components to a secure and supported version.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
Bumps nokogiri from 1.15.3 to 1.19.4.
Release notes
Sourced from nokogiri's releases.
... (truncated)
Changelog
Sourced from nokogiri's changelog.
... (truncated)
Commits
8cfb9daversion bump to v1.19.4a856d1efix: JRuby NONET bypass in XML::Schema (v1.19.x) (#3639)6a0aa1efix(CRuby): use-after-free in Document#encoding= when setter raises (v1.19.x)...f658a54fix: JRuby NONET bypass in XML::Schema39d26fefix(CRuby): use-after-free in Document#encoding= when setter raises04a09ddfix(CRuby): out-of-bounds read in NodeSet#[] with large negative index (v1.19...7799fbdfix: avoid NPE on uninitialized XML::Node structs (v1.19.x) (#3645)ef19e13fix(CRuby): avoid UAF in XML::Attr#value= (v1.19.x) (#3644)5524fa9fix:Document#root=rejects non-element nodes (v1.19.x) (#3643)9891ad1fix(CRuby): use-after-free in XPathContext document lifetime (v1.19.x) (#3641)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.