Skip to content

Conversation

@razumau
Copy link
Contributor

@razumau razumau commented Aug 12, 2025

Drops support for EOL versions of Ruby (even 3.1 is actually EOL at this time, but we’ll leave it for now).

Checks in Gemfile.lock (I spent some time figuring out why some tests failed on Ruby 2.7 but not 3.4, and that was because different versions of faraday got installed for 2.7 and 3.4).

Updates rubocop and applies a bunch of cops.

In CI workflow: uses correct main branch, updates checkout and setup-ruby actions, runs spec-live on Ruby 3.4, adds JRuby 10, removes unnecessary bundle install.

To do in follow-up PRs: remove limits on rspec gems, simplify Gemfile.

@razumau razumau force-pushed the jury.razumau/modernise_workflows branch 4 times, most recently from 3be57b9 to 9a9b00d Compare August 12, 2025 17:19
@razumau razumau changed the title update CI workflow drop support for Ruby 2.7 and 3.0, update CI Aug 12, 2025
@razumau razumau marked this pull request as ready for review August 12, 2025 17:26
@razumau razumau requested a review from a team as a code owner August 12, 2025 17:26
@razumau razumau requested a review from a team August 12, 2025 17:26
s.files = Dir.glob('{lib,util}/**/*') << 'LICENSE'

s.required_ruby_version = ">= 2.7"
s.required_ruby_version = ">= 3.1"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we know (do we have a way of knowing) which version our users are using?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Theoretically, RubyGems.org’s download logs would have Ruby versions.
Realistically, customers can complain to our support and convince us to continue supporting older versions. So I think we should just scream-test this.

Uses correct main branch, updates checkout and setup-ruby actions, runs spec-live on Ruby 3.4, adds JRuby 10, removes unnecessary `bundle install`.
A ceiling was originally introduced “just in case” before hashie 4.0 (11 years ago: f54ad72, see also e73fa18), and then only the value has been updated (to 5.x and 6.x). This means unnecessary difficulties when a new major version of hashie comes out without any gains, so let’s just drop it.
@razumau razumau force-pushed the jury.razumau/modernise_workflows branch from 9a9b00d to 911e887 Compare August 14, 2025 12:13
@razumau razumau merged commit ab34ca8 into main Aug 25, 2025
7 checks passed
@razumau razumau deleted the jury.razumau/modernise_workflows branch August 25, 2025 06:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants