[Snyk] Fix for 30 vulnerabilities

[Rubix982]

Snyk has created this PR to fix 30 vulnerabilities in the rubygems dependencies of this project.

Snyk changed the following file(s):

• docs/Gemfile
• docs/Gemfile.lock

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Heap-based Buffer Overflow SNYK-RUBY-NOKOGIRI-7164639	696
	Stack-based Buffer Overflow SNYK-RUBY-NOKOGIRI-8732769	671
	Use After Free SNYK-RUBY-NOKOGIRI-8732779	671
	Uncontrolled Resource Consumption ('Resource Exhaustion') SNYK-RUBY-REXML-7577227	666
	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-3318400	646
	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-5829860	641
	Improper Handling of Unexpected Data Type SNYK-RUBY-NOKOGIRI-2840634	624
	Improper Restriction of XML External Entity Reference ('XXE') SNYK-RUBY-REXML-7814166	624
	Regular Expression Denial of Service (ReDoS) SNYK-RUBY-NOKOGIRI-2620374	589
	Out-of-bounds Write SNYK-RUBY-NOKOGIRI-2630623	589
	Denial of Service (DoS) SNYK-RUBY-NOKOGIRI-2630898	589
	NULL Pointer Dereference SNYK-RUBY-NOKOGIRI-3052880	589
	Directory Traversal SNYK-RUBY-TZINFO-2958048	589
	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-5603112	586
	Use After Free SNYK-RUBY-NOKOGIRI-9510795	576
	Denial of Service (DoS) SNYK-RUBY-REXML-7577228	559
	Regular Expression Denial of Service (ReDoS) SNYK-RUBY-REXML-8309365	559
	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-3318401	536
	Use After Free SNYK-RUBY-NOKOGIRI-6228056	524
	Cross-site Scripting (XSS) SNYK-RUBY-ACTIVESUPPORT-3360028	519
	Out-of-bounds Read SNYK-RUBY-COMMONMARKER-3318398	486
	Regular Expression Denial of Service (ReDoS) SNYK-RUBY-ACTIVESUPPORT-3237242	479
	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-5603111	479
	Uncontrolled Resource Consumption SNYK-RUBY-REXML-6861566	479
	Denial of Service (DoS) SNYK-RUBY-REXML-7462086	479
	Use After Free SNYK-RUBY-NOKOGIRI-9510789	469
	Information Exposure SNYK-RUBY-ACTIVESUPPORT-5851458	429
	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-3318399	429
	Buffer Under-read SNYK-RUBY-NOKOGIRI-9789079	426
	Cross-site Scripting (XSS) SNYK-RUBY-NOKOGIRI-8453714	319

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Cross-site Scripting (XSS)
🦉 Use After Free
🦉 More lessons are available in Snyk Learn

Summary by Sourcery

Upgrade documentation dependencies to address 30 security vulnerabilities flagged by Snyk

Enhancements:

• Upgrade Jekyll to 3.9.1 and GitHub Pages to v226 for security fixes
• Bump jekyll-paginate-v2 to 2.0 and jekyll-feed to 0.16.0 to resolve vulnerabilities

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sourcery-ai]

Reviewer's Guide

This PR addresses security vulnerabilities by upgrading key RubyGem dependencies in the docs Gemfile—adjusting version constraints for jekyll, GitHub Pages, jekyll-paginate-v2, and jekyll-feed—and regenerates the lock file accordingly.

File-Level Changes

Change	Details	Files
Bump jekyll to patch release	Update gem "jekyll" constraint from "> 3.9.0" to "> 3.9.1"	docs/Gemfile docs/Gemfile.lock
Raise minimum GitHub Pages version	Change gem "github-pages" requirement from ">= 224" to ">= 226"	docs/Gemfile docs/Gemfile.lock
Upgrade jekyll-paginate-v2 to v2.0	Adjust gem "jekyll-paginate-v2" from "> 1.9", ">= 1.9.4" to "> 2.0", ">= 2.0.0"	docs/Gemfile docs/Gemfile.lock
Update jekyll-feed to 0.16.0	Change gem 'jekyll-feed' requirement from '>= 0.15.1' to '>= 0.16.0'	docs/Gemfile docs/Gemfile.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.