New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[deps] update Rubygems to latest 3.1 (3.1.6) #6294
Conversation
I think this might be because of some bugs that I introduced in rubygems 3.1 require 😞. Cherry-picking recent PRs fixing require issues should probably do the trick: |
Thanks David, will those PRs get a backport for 3.1 or will the only land in 3.2? |
I think there's an intention to backport these fixes to rubygems 3.1.5 and include them with ruby 2.7.2. At least @hsbt assigned this ruby-core ticket to himself after I suggested it. |
@deivid-rodriguez For context, we want to release JRuby 9.2.12 with RubyGems 3.1, but we need these fixes present. We are naturally reluctant to patch our shipped version of RubyGems if it's possible an upgrade will wipe them out. |
Thanks! @kares already explained that in rubygems/rubygems#3751, and it sounds totally reasonable to me. |
FWIW, 3.1.6 was released with these backports: https://blog.rubygems.org/2021/01/26/3.1.6-released.html. |
@deivid-rodriguez Thank you! @enebo Updating RubyGems is probably way out of scope for 9.2.17.0 but perhaps .18? cc @kares |
* jruby-9.2: (181 commits) Update jar-dependencies Update Ruby version to 2.5.8 Update io/console to the gem version Update Rake to match 2.5.8 Update stdlib from 2.5.8 Update for new launcher Untag passing zlib deflate specs Return inflate content, not finish result Only include gems in bundled or default Detect modules more robustly Restructure Set factory methods Missed change in pom.xml Remove the bin/ruby script from stdlib artifact Restore gem dir location for default bins Remove files installed by bundled gems Simplify bundled and default gem installs Include all of preinstalled + default gem contents Update for next dev cycle Remove wrong and extraneous constant assignment Update for 9.2.16.0 ...
targeting for 9.2.12
failing 2 ruby specs atm - needs investigation as RGs changed path handling: