[Snyk] Security upgrade github-pages from 207 to 207

[snyk-bot]

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.lock

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	661/1000 Why? Recently disclosed, Has a fix available, CVSS 7.5	Directory Traversal SNYK-RUBY-TZINFO-2958048	No	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:

🦉 Directory Traversal

[github-learning-lab]

I was expecting your file to be named _posts/0000-01-02-rlibbert.md.

Let's edit this pull request to fix both of these issues.

⌨️ Activity: Fixing your pull request

1. Click the Files Changed tab in this pull request.
2. Verify that the only file edited is named _posts/0000-01-02-rlibbert.md.
3. If the file is improperly named, or not in a proper location, use the edit function to correct it.
4. Above the contents of the file, select all text in the field that contains the filename and delete it.
5. Continue pressing your backspace key to also delete any directory names that exist.
6. Type the proper filename:

   _posts/0000-01-02-rlibbert.md

7. Scroll to the bottom and enter a commit message and commit in the Commit Changes section.

Note: Can't find the button to edit the file? It may look like a pencil, or it may look like three dots.

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.

---

I'll respond below when I detect a commit on this branch.