Bump nokogiri from 1.6.1 to 1.19.3#6
Conversation
Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.6.1 to 1.19.3. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md) - [Commits](sparklemotion/nokogiri@v1.6.1...v1.19.3) --- updated-dependencies: - dependency-name: nokogiri dependency-version: 1.19.3 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit d8db8f7. Configure here.
| jwt (~> 0.1.8) | ||
| nokogiri (1.19.3) | ||
| mini_portile2 (~> 2.8.2) | ||
| racc (~> 1.4) |
There was a problem hiding this comment.
Nokogiri is orphaned in lockfile with no dependents
Low Severity
nokogiri is listed in the resolved gems but nothing in the dependency graph actually requires it. The old github_api 0.11.3 depended on nokogiri (~> 1.6.0), but the updated github_api 0.19.0 dropped that dependency. Since nokogiri isn't in the Gemfile either, it's now an orphaned entry that will be installed unnecessarily (including its native extensions). The security fix this PR aims to apply is effectively a no-op since the gem isn't actually used.
Reviewed by Cursor Bugbot for commit d8db8f7. Configure here.
Bumps nokogiri from 1.6.1 to 1.19.3.
Release notes
Sourced from nokogiri's releases.
... (truncated)
Changelog
Sourced from nokogiri's changelog.
... (truncated)
Commits
c139a3dversion bump to v1.19.37501a63fix: backtracking in CSS tokenizer rules (v1.19.x backport) (#3627)03e7968test: skip CSS tokenizer benchmarks on JRubyb984b7efix: ReDoS in CSS tokenizer ident rule0092623fix: ReDoS in CSS tokenizer STRING ruleee17d33fix: memory leak in XSLT transform (backport to v1.19.x) (#3624)ce188a3doc: update CHANGELOGcaeaac4fix: memory leak in XSLT transform25220bfdep(test): test against libxml-ruby v6 (#3618)0caeb21doc: add security warnings for untrusted XSLT stylesheetsDependabot 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.
Note
Medium Risk
Large dependency upgrade in
Gemfile.lock(notablynokogiri1.6.1→1.19.3) plus multiple transitive bumps (e.g.,faraday,github_api,jwt) could introduce runtime incompatibilities despite no application code changes.Overview
Updates locked Ruby dependencies, primarily bumping
nokogirifrom1.6.1to1.19.3.This refresh also upgrades related/transitive gems (notably
github_apiand thefaradaystack, plusjwt/oauth2) and adds new lockfile entries required by the newer versions.Reviewed by Cursor Bugbot for commit d8db8f7. Bugbot is set up for automated code reviews on this repo. Configure here.