Age | Commit message (Collapse) | Author |
|
https://github.com/rubygems/rubygems/commit/fe723c0f7f
|
|
https://github.com/rubygems/rubygems/commit/8bf41f53cc
|
|
https://github.com/rubygems/rubygems/commit/e5532ef886
|
|
Mitigate the security risk:
https://devcraft.io/2021/01/07/universal-deserialisation-gadget-for-ruby-2-x-3-x.html
https://github.com/rubygems/rubygems/commit/141c2f4388
|
|
After reading [this blog
post](https://blog.rubygems.org/2011/08/31/shaving-the-yaml-yak.html),
published almost 10 years ago already, my understanding is that this
problem could come up in two ways:
* Rubygems.org serving corrupted gemspecs". As far as I understand this
was fixed in rubygems.org a lot time ago, since
https://github.com/rubygems/rubygems.org/pull/331.
* Clients having a ten years old gemspec cache with some of these bad
gemspecs. In this case, there's no easy solution but I think ten years
is enough and rebuilding the cache should do the trick.
So, I think it's time we remove this.
https://github.com/rubygems/rubygems/commit/afcb15d556
|
|
https://github.com/rubygems/rubygems/commit/c4004fadd9
|
|
[Fixes #4733]
https://github.com/rubygems/rubygems/commit/fce7f3eb7d
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4648
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4634
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4533
|
|
https://github.com/rubygems/rubygems/commit/aa390a3500
|
|
* Port
https://github.com/ruby/ruby/commit/8e91b969df08b7a2eb27a5d6d38733eea42dc7ad
from ruby-core, and make it compatible with psych 3 & 4.
|
|
https://github.com/rubygems/rubygems/commit/e7280f8d30
Notes:
Merged: https://github.com/ruby/ruby/pull/4491
|
|
https://github.com/rubygems/rubygems/commit/83ebdec27a
Notes:
Merged: https://github.com/ruby/ruby/pull/4491
|
|
https://github.com/rubygems/rubygems/commit/795b572ac2
Notes:
Merged: https://github.com/ruby/ruby/pull/4491
|
|
https://github.com/rubygems/rubygems/commit/ae44b68d57
Notes:
Merged: https://github.com/ruby/ruby/pull/4491
|
|
https://github.com/rubygems/rubygems/commit/a10ff97830
Notes:
Merged: https://github.com/ruby/ruby/pull/4491
|
|
test/rubygems/test_gem_remote_fetcher.rb
https://github.com/rubygems/rubygems/commit/f1af59fe02
Notes:
Merged: https://github.com/ruby/ruby/pull/4491
|
|
https://github.com/rubygems/rubygems/commit/8b2ca6df3a
Notes:
Merged: https://github.com/ruby/ruby/pull/4491
|
|
of assert_path_exists and refute_path_exists
https://github.com/rubygems/rubygems/commit/a7c93558c3
Notes:
Merged: https://github.com/ruby/ruby/pull/4491
|
|
https://github.com/rubygems/rubygems/commit/a8571524ad
Notes:
Merged: https://github.com/ruby/ruby/pull/4491
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4367
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4383
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4143
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4117
|
|
This reverts commit 80bad36989bbc4ad6167fe9670327f95b78089ce,
because a few CI machines fail continuously.
|
|
For each `make check`, rubygems test makes "tmp" directory and
some "gem_generate_index..." directories remain there.
* Do not create a (fixed name) directory in the current working
directory
* Should remove its own temporary directory
Notes:
Merged: https://github.com/ruby/ruby/pull/4115
|
|
iff means if and only if, but readers without that knowledge might
assume this to be a spelling mistake. To me, this seems like
exclusionary language that is unnecessary. Simply using "if and only if"
or "whether" should suffice.
https://github.com/rubygems/rubygems/commit/88318ebc6d
|
|
55634a8af18a52df86c4275d70fa1179118bcc20
Notes:
Merged: https://github.com/ruby/ruby/pull/4021
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3982
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3930
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3901
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3729
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3864
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3854
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3660
|
|
On my system, the error was being hidden by the presence of a YARD
rubygems plugin that was providing the require and making things work.
|
|
Sometimes "install_dir/cache" directory is not writable although "install_dir" is writable.
https://github.com/rubygems/rubygems/commit/665221cb69
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
As far as I could see, `Gem::Resolver::APISpecification` objects are
supposed to be immutable. If my guessing is correct, then we can cache
and reuse its instances for performance.
At least, `rake` passes on my machine.
Before this change:
```
$ time ruby -I lib bin/gem install --no-doc aws-sdk
Successfully installed aws-sdk-3.0.1
1 gem installed
real 0m37.104s
user 0m36.952s
sys 0m0.333s
```
After this change:
```
$ time ruby -I lib bin/gem install --no-doc aws-sdk
Successfully installed aws-sdk-3.0.1
1 gem installed
real 0m23.905s
user 0m23.740s
sys 0m0.365s
```
https://github.com/rubygems/rubygems/commit/7e8fbba85c
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
https://github.com/rubygems/rubygems/commit/d498ae3d62
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
--system --silent`
https://github.com/rubygems/rubygems/commit/038203aaf8
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
https://github.com/rubygems/rubygems/commit/c3fb0db930
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
https://github.com/rubygems/rubygems/commit/5a1e56e892
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
https://github.com/rubygems/rubygems/commit/dd87d70f51
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
Consider the version original included with each ruby as the minimum
supported version.
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
help message
https://github.com/rubygems/rubygems/commit/38230a77c1
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|
|
https://github.com/rubygems/rubygems/commit/087a1f9720
Notes:
Merged: https://github.com/ruby/ruby/pull/3599
|