Skip to content

Conversation

@CookiePLMonster
Copy link
Contributor

  • Update actions/checkout
  • Update the Ruby versions matrix to 2.5 (lowest supported) and all currently maintained Ruby versions (3.2-3.4)

I kept 2.5 in the build matrix as it's the lowest supported Ruby version in the .gemspec file. I'm not sure if it makes sense to keep 2.7 around, so I instead opted for the currently supported versions. For CI actions that deal with both Jekyll 3.x and 4.x, I opted to use Ruby 3.2 as the oldest currently maintained version, as Jekyll 3.x doesn't work with Ruby 3.4 due to the base64 dependency no longer being part of the standard library. For tests, I wasn't sure what Ruby version to use so I left it at 2.5.

* Update actions/checkout
* Update the Ruby versions matrix to 2.5 (lowest supported by the gem)
   and all currently maintained Ruby versions (3.2-3.4)
@CookiePLMonster
Copy link
Contributor Author

Should the version matrix perhaps align with Jekyll 4.x https://github.com/jekyll/jekyll/blob/master/.github/workflows/ci.yml#L25-L30 + Ruby 2.5 as the lowest supported version?

@ashmaroli ashmaroli changed the title Update CI actions Bump versions in workflows May 5, 2025
So that `ruby/setup-ruby` actions installs a version of **Rubygems**
newer than `2.7.6.3`.
Newer versions of Rubygems contain a patch that allows Bundler to
honour `required_ruby_version` directive properly
@CookiePLMonster
Copy link
Contributor Author

If CI jobs are running against 2.7, should the minimum Ruby requirement for this gem be bumped too?

@ashmaroli
Copy link
Member

If CI jobs are running against 2.7, should the minimum Ruby requirement for this gem be bumped too?

Not necessarily. The plugin can still be installed and run on Ruby 2.5 and Ruby 2.6 (albeit no longer tested with and therefore no longer recommended).
We bump the required Ruby-version when we introduce Ruby 2.7-specific syntax in lib files.

@ashmaroli
Copy link
Member

Thanks @CookiePLMonster
@jekyllbot: merge +dev

@jekyllbot jekyllbot merged commit 5bff353 into jekyll:master May 5, 2025
8 checks passed
jekyllbot added a commit that referenced this pull request May 5, 2025
@CookiePLMonster CookiePLMonster deleted the ruby-matrix-upgrade branch May 5, 2025 11:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants