You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before I migrate my app from 3.1 to 3.2, I need to validate that sift-ruby works with ruby version 3.2.
To validate the gem, I have checked out the sift-ruby repository and run bundle exec rspec. The rspec tests pass with ruby version 3.1, but they fail with ruby version 3.2. Part of the failure in 3.2 is that the rspec library is too old, and it uses methods that have been removed in 3.2. But even after upgrading the rspec library, I am still seeing test errors in ruby 3.2:
It looks like this gem needs to be revisited to support ruby 3.2. Since ruby 3.1 will be EOL in the first quarter of next year, are there any plans to update this gem before then?
The text was updated successfully, but these errors were encountered:
Altough I agree some of the gems might require upgrading however my run fully green on 3.2.6 and i'm not able to reproduce what you are seeing and it's hard to say what is wrong on your side without more details of your setup.
Before I migrate my app from 3.1 to 3.2, I need to validate that sift-ruby works with ruby version 3.2.
To validate the gem, I have checked out the sift-ruby repository and run
bundle exec rspec
. The rspec tests pass with ruby version 3.1, but they fail with ruby version 3.2. Part of the failure in 3.2 is that the rspec library is too old, and it uses methods that have been removed in 3.2. But even after upgrading the rspec library, I am still seeing test errors in ruby 3.2:It looks like this gem needs to be revisited to support ruby 3.2. Since ruby 3.1 will be EOL in the first quarter of next year, are there any plans to update this gem before then?
The text was updated successfully, but these errors were encountered: