[Snyk] Security upgrade github-pages from 225 to 226

[Rubix982]

Snyk has created this PR to fix 5 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
	Expired Pointer Dereference SNYK-RUBY-NOKOGIRI-10674179	726
	Stack-based Buffer Overflow SNYK-RUBY-NOKOGIRI-10674176	721
	Expired Pointer Dereference SNYK-RUBY-NOKOGIRI-10674184	721
	Out-of-bounds Read SNYK-RUBY-NOKOGIRI-10674192	721
	Stack-based Buffer Overflow SNYK-RUBY-NOKOGIRI-10674188	376

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Summary by Sourcery

Bug Fixes:

• Bump github-pages gem requirement from 224 to 226 in docs to address high-severity Nokogiri vulnerabilities

[sourcery-ai]

Reviewer's Guide

This PR upgrades the github-pages dependency from version 225 to 226 in the docs site to incorporate security fixes (notably for Nokogiri vulnerabilities), implemented by bumping the Gemfile version requirement and regenerating the Gemfile.lock.

File-Level Changes

Change	Details	Files
Bump github-pages gem requirement	Updated github-pages version constraint from >= 224 to >= 226 in docs/Gemfile	docs/Gemfile
Regenerate lockfile to apply updated dependencies	Refreshed docs/Gemfile.lock with new dependency resolutions	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.

[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.}