this post was submitted on 24 Jul 2023
8 points (100.0% liked)
Ruby
530 readers
1 users here now
A community for discussion and news about Ruby programming.
Learning Ruby?
- Try Ruby in your browser
Tools
- Ruby Version Manager (RVM) Install, manage and work with multiple Ruby environments. adsf is an increasingly popular option too.
- rbenv Groom your app’s Ruby environment with rbenv.
- Looking for new gems? ruby-toolbox
- Install Ruby on macOS
Documentation
- Ruby API or Ruby Doc
- YARD docs via rubydoc.info YARD Documentation Server
Books
- Well Grounded Rubyist
- Eloquent Ruby
- Metaprogramming Ruby
- Effective Testing with RSpec 3
- Programming Ruby 1.9: The Pragmatic Programmers’ Guide
- The Ruby Programming Language
Screencasts
News and updates
- Ruby news in a weekly email from Ruby Weekly
- 'Planet' of Ruby blogs at rubyland.news
- Ruby tweets at @RubyInside
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Assuming it's properly tested, I would simply run the tests that apply to the code in this directory with the versions of Ruby you're trying to ensure compatibility with.
If you're using GitHub Actions for CI, then you can create jobs for each version of Ruby you're trying to use. Then, ensure your default branch is protected, and set your branch protections only allows PRs to merge that pass CI.
This will also ensure that Ruby 3.x.x works with your current code, too. Some things have been deprecated, i.e.
File#exists?
has been removed in favor ofFile#exist?
Also, this sounds like a good case of submodules, if this code is used for various projects.