Skip to content

THREESCALE-11894 - Bump nokogiri gem [2.15]#600

Open
akostadinov-bot[bot] wants to merge 2 commits into
3scale-2.15-stablefrom
THREESCALE-11894-bump-nokogiri-2.15
Open

THREESCALE-11894 - Bump nokogiri gem [2.15]#600
akostadinov-bot[bot] wants to merge 2 commits into
3scale-2.15-stablefrom
THREESCALE-11894-bump-nokogiri-2.15

Conversation

@akostadinov-bot

Copy link
Copy Markdown

Summary

  • Bump nokogiri from 1.16.5 to 1.19.4 in Gemfile.lock
  • Picks up latest libxml2 fixes bundled with the nokogiri gem
  • No changes to Gemfile constraints; all existing dependency requirements remain satisfied

Test plan

  • CI passes (Gemfile.lock only change, no code changes)
  • Verify the application boots correctly with the updated gem

akostadinov-bot and others added 2 commits July 10, 2026 17:24
Bump nokogiri gem from 1.16.5 to 1.19.4 to pick up
the latest libxml2 fixes bundled with the gem.

Assisted-By: claude-opus-4-6
nokogiri 1.19.x requires Ruby >= 3.2, but this branch's Dockerfile
uses ubi9/ruby-31 (Ruby 3.1). Downgrade to 1.18.10, the latest
version compatible with Ruby 3.1. Dependencies (mini_portile2 ~> 2.8.2,
racc ~> 1.4) remain unchanged.

Assisted-By: claude-opus-4-6
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@akostadinov-bot

Copy link
Copy Markdown
Author

Review finding: Ruby version incompatibility (fixed)

Issue: nokogiri 1.19.4 requires Ruby >= 3.2, but this branch (3scale-2.15-stable) uses ubi9/ruby-31 (Ruby 3.1) in its Dockerfile. Bumping to 1.19.4 would break the build.

Fix pushed: Changed the bump target to nokogiri 1.18.10 (latest in the 1.18.x series), which requires Ruby >= 3.1.0 and is compatible with this branch's Ruby version. Dependencies (mini_portile2 ~> 2.8.2, racc ~> 1.4) remain the same.

Version Required Ruby Compatible?
1.16.5 (current) >= 3.0.0 Yes
1.18.10 (fixed) >= 3.1.0 Yes
1.19.4 (original PR) >= 3.2 No

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants