diff options
| author | David RodrÃguez <deivid.rodriguez@riseup.net> | 2023-12-07 14:51:22 +0100 |
|---|---|---|
| committer | Hiroshi SHIBATA <hsbt@ruby-lang.org> | 2023-12-12 10:04:57 +0900 |
| commit | a06bf001b29bba77e71ba270f73469d9c9b4b0f0 (patch) | |
| tree | 79f807c1585a0fbe667db0e6de9c26a93ff39409 /spec/ruby/core/basicobject/basicobject_spec.rb | |
| parent | b37288c047681e02615b5b484fb265b394ddc612 (diff) | |
[rubygems/rubygems] Remove non-transparent requirement added to prerelease gems
I think we can safely assume these days that all RubyGems and Bundler
versions that will ever bundle a new gem created in 2023 support
prereleases.
So this non transparent requirement is not necessary.
In my opinion, it should be the gem author to explicitly add this
constraint, not RubyGems.
https://github.com/rubygems/rubygems/commit/b165e6d725
Diffstat (limited to 'spec/ruby/core/basicobject/basicobject_spec.rb')
0 files changed, 0 insertions, 0 deletions