The behavior should be identical to what we saw before.
open(...).read got deprecated in Ruby 3.0
Do you think it's worth adding an integration test for this on CI?
Something like this would probably work to sanity check this. Probably would need to add more Rubies to CI though to make it a better check. Maybe not worth the effort.
These changes should be backwards compatible with older Ruby versions according to the docs and testing it on Ruby 2.7 and 3.2.
Changes:
require_relative
to avoid loading errors.URI.parse(...).read
instead ofopen(...).read
open(...).read
got deprecated in Ruby 3.0Do you think it's worth adding an integration test for this on CI?
Something like this would probably work to sanity check this. Probably would need to add more Rubies to CI though to make it a better check. Maybe not worth the effort.