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 @headius do we need to manually merge something then. 9.1.6.0 is coming out today/tomorrow so if we need something patched in 2.6.8 we should get it done pronto :)

@enebo etehtsea@63fcab8

@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.