LuciferYang opened a new pull request, #83:
URL: https://github.com/apache/gluten-site/pull/83

   Bumps the gems behind 36 of the 37 open Dependabot alerts. Only 
`Gemfile.lock` changes. It was regenerated with `bundle lock --conservative 
--update` for the gems below, so their dependencies stay at the locked versions 
unless a new release requires otherwise.
   
   | gem | before | after | alerts |
   |-|-|-|-|
   | nokogiri | 1.16.2 | 1.19.5 | 16 |
   | rexml | 3.2.6 | 3.4.4 | 6 |
   | activesupport | 7.1.3 | 8.1.4 | 3 |
   | concurrent-ruby | 1.2.3 | 1.3.8 | 3 |
   | faraday | 2.9.0 | 2.15.1 | 3 |
   | uri | 0.13.0 | 1.1.2 | 2 |
   | webrick | 1.8.1 | 1.9.2 | 2 |
   | addressable | 2.8.6 | 2.9.2 | 1 |
   
   The new activesupport and faraday pull in json, logger and securerandom, and 
activesupport 8 drops mutex_m. nokogiri 1.19 has no prebuilt gem for the 
`x86-linux` platform in the lockfile, so the lock also gets a source `nokogiri` 
entry and mini_portile2.
   
   nokogiri 1.19 requires Ruby 3.2 or newer, so building the site does too. The 
ASF Jekyll builder already has a new enough Ruby: accumulo-website moved its 
lockfile to nokogiri 1.19.4 on 2026-10-28, and the build it triggered on the 
same builder succeeded ([build 
3279](https://ci2.apache.org/#/builders/7/builds/3279)).
   
   The rubyzip alert is not fixed here. It needs rubyzip 3.x, but 
`github-pages` pins `jekyll-remote-theme` 0.4.3, which requires `rubyzip < 
3.0`. That needs its own change.
   
   ### How was this patch tested?
   
   Built the site with the old and the new lockfile using `bundle install && 
bundle exec jekyll build`, the same steps the ASF Jekyll builder runs, in a 
`ruby:3.2` container on x86_64 and arm64. The generated `_site` trees are 
identical apart from build timestamps.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to