Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed in https://github.com/github/pages/pull/2086 that jekyll-seo-tag v2.5.0 requires Ruby 2.3 or greater.
As it turns out, Ruby 2.2 is now EOL, and Ruby 2.3 is EOL in March 2019. https://www.ruby-lang.org/en/news/2018/06/20/support-of-ruby-2-2-has-ended/
In the Jekyll project, it was our general understanding that we would drop support for a minor bump of Ruby only explicitly (i.e. require something higher) in a major version bump of Jekyll. In GitHub Pages, we don't have that same issue, since every version bump is a major version bump.
Generally speaking, supporting an EOL Ruby version is ill-advised. An EOL version doesn't receive security patches, and may have bugs that will never be fixed. By targeting Ruby 2.3 or higher, we can eliminate the likelihood that our users are exposed to any security vulnerabilities that are discovered in Ruby 2.2 and earlier.
Ruby version constraints are heavy-handed, but upgrading is key to keeping our community safe and progressing.