[Snyk] Security upgrade github-pages from 212 to 224

[abood640]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `rubygems` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • Gemfile

⚠️ Warning

Failed to update the Gemfile.lock, please update manually before merging.

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	558/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 3.3	Out-of-bounds Read SNYK-RUBY-COMMONMARKER-3318398	Yes	Proof of Concept
	461/1000 Why? Recently disclosed, Has a fix available, CVSS 3.5	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-3318399	Yes	No Known Exploit
	668/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.5	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-3318400	Yes	Proof of Concept
	461/1000 Why? Recently disclosed, Has a fix available, CVSS 3.5	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-3318401	Yes	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Denial of Service (DoS)
🦉 Denial of Service (DoS)
🦉 Denial of Service (DoS)

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.