-
-
Notifications
You must be signed in to change notification settings - Fork 11
Description
Issue Summary
The sorted_set
gem specifies a dependency on set (~> 1.0)
, which allows versions up to 1.1.0
but excludes 1.1.1
.
However, in Ruby 3.4.1, set 1.1.1
is installed as a default gem, which causes a dependency conflict when using sorted_set
.
How I Noticed This Issue
I encountered this issue while running a job that depends on sorted_set
. The job failed with the following error:
Gem::LoadError: You have already activated set 1.1.1, but your Gemfile requires set 1.1.0. Since set is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports set as a default gem. (Gem::LoadError)
Expected Behavior
sorted_set
should be compatible with set 1.1.1
, as it is the default gem in Ruby 3.4.1
.
Actual Behavior
sorted_set
requiresset (~> 1.0)
, which allows up to1.1.0
but not1.1.1
- This results in a dependency conflict when using Ruby
3.4.1
Suggested Solution
- Update the dependency in
sorted_set.gemspec
toset (~> 1.1)
to allow compatibility with Ruby3.4.1
- Or confirm whether
sorted_set
should continue to enforceset (~> 1.0)
Environment
- Ruby Version: 3.4.1
- sorted_set Version: 1.0.3
- set Version (default gem in Ruby 3.4.1): 1.1.1
- Bundler Version: (2.3.26)
This issue makes it impossible to use sorted_set
with Ruby 3.4.1 without manually downgrading set
to 1.1.0, which is not ideal.
Would you consider updating the dependency to be compatible with set 1.1.1
?