-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
Update RubyGems #4205
Comments
2.6.8 version still don't have fix for the #4019. |
@etehtsea Is this change about not landing non-standard gems in stdlib the fix which will help #4019? |
@olleolleolle as far as I remember, these two are unrelated. |
@etehtsea I'm confused then. rubygems/rubygems#1685 was merged August 17, 2.6.8 was released since then,, and I see rubygems/rubygems@d98f036 on master. But the version in 2.6.8 does not appear to have your change. I'm rather confused. Can you clarify why this fix is not in the release, @segiddins? FWIW, this is largely a cosmetic fix, so if we have to apply a manual patch to get it perhaps we just don't bother for now. |
Because we only backport critical big fixes in patch releases. Default is commits must wait until a new minor. |
RubyGems is current for 9.2. |
In #4198, which fixes #4019, we manually patched our in-repo copy of RubyGems. We'll need to move to an unpatched release once rubygems/rubygems#1685 is released.
The text was updated successfully, but these errors were encountered: