| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
55634a8af18a52df86c4275d70fa1179118bcc20
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
--system --silent`
https://github.com/rubygems/rubygems/commit/038203aaf8
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/c3fb0db930
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/5a1e56e892
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/dd87d70f51
|
|
|
|
|
| |
Consider the version original included with each ruby as the minimum
supported version.
|
|
|
|
|
|
| |
help message
https://github.com/rubygems/rubygems/commit/38230a77c1
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/087a1f9720
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/1715610648
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/addc644cad
|
| |
|
|
|
|
|
| |
31a6eaabc165d8a222e176f2c809d90622d88ec2 is obsoleted with
https://github.com/rubygems/rubygems/pull/3820
|
|
|
|
| |
Enable Style/EmptyLinesAroundClassBody rubocop cop.
|
|
|
|
|
|
|
|
| |
This restores 3.0 behavior and goes back to not formatting executables
by default on `gem update --system`. This is friendlier for jruby and
doesn't really affect OS packagers.
https://github.com/rubygems/rubygems/commit/1a504b651d
|
|
|
|
|
|
| |
Since `rubygems/util` is autoloaded.
https://github.com/rubygems/rubygems/commit/52a9f88b99
|
|
|
|
|
|
| |
The `rubygems/security` require already does this.
https://github.com/rubygems/rubygems/commit/bbb444b6f1
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/2cca6714f3
|
|
|
|
| |
To normalize the code style with `bundler`.
|
| |
|
| |
|
|
|
|
| |
To make rubygems code style consistent with bundler.
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/10cc79ee21
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/a82a77251d
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/97772bb066
|
|
|
|
|
|
|
|
| |
The file was removed at
https://github.com/rubygems/rubygems/commit/65b709b095b8354ac2620d1a5d7d537e539f6498,
shipped with rubygems 2.6.5.
https://github.com/rubygems/rubygems/commit/739159a120
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/28d6d77d81
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/8cc6087590
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/6ddbf5bcab
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/5106ea4582
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/fb824b7a81
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/6dc76146ad
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently `gem uninstall --all` shows the following incorrect message
after completion:
```
INFO: Uninstalled all gems in
```
Now it shows something that actually makes sense like:
```
INFO: Uninstalled all gems in /home/deivid/Code/rubygems/tmp/test_rubygems_6986/gemhome
```
https://github.com/rubygems/rubygems/commit/8fa05e8f8c
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/1e5ef177ac
|
|
|
|
|
|
|
|
|
|
| |
`@host` _could_ be `nil` at this point, but only if all the conditions
above for setting `@host` were `nil`. In that case, it is guaranteed
to `default_gem_server` metadata is `nil` since it's one of the
branches in that condition. So this code would just be setting an
already `nil` variable to `nil`. Hence, not needed.
https://github.com/rubygems/rubygems/commit/e3ccff3c5c
|
|
|
|
|
|
|
|
|
| |
This block was a branch and variable heavy way of saying use the
user-provided host if available, or fall-back to the default host if
none of the other options match. IMO the resultant single-if condition
is clearer in intentions
https://github.com/rubygems/rubygems/commit/42dbb71cfa
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/6afd914fda
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/4fe5bb5bf3
|
|
|
|
|
|
|
| |
English.rb is extracted to the default gems at
https://github.com/ruby/ruby/commit/2c5764ec223d976e0d0da1494596a1519104be3e
https://github.com/rubygems/rubygems/commit/532f488c0b
|
|
|
|
|
|
| |
So it matches the style used by bundler.
https://github.com/rubygems/rubygems/commit/ab0580fd65
|
| |
|
|
|
|
| |
The original commit was https://github.com/rubygems/rubygems/pull/3119
|
|
|
|
|
|
|
|
|
|
|
|
| |
This condition is too restrictive in my opinion. If a user has a pre
version of rubygems installed, she should be fully responsible for it,
and we shouldn't restrict any functionality.
Also, why is a new prerelease disallowed but an old prelease allowed, or
why is 2.0.0.rc2 explictly whitelisted? I believe this kind of
exceptions are one more reason to actually permit this.
https://github.com/rubygems/rubygems/commit/7f77a77620
|
|
|
|
| |
Just started to develop RubyGems 3.2.0.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix gem pristine not accounting for user installed gems. Pull request
#2914 by Luis Sagastume.
* Refactor keyword argument test for Ruby 2.7. Pull request #2947 by
SHIBATA Hiroshi.
* Fix errors at frozen Gem::Version. Pull request #2949 by Nobuyoshi
Nakada.
* Remove taint usage on Ruby 2.7+. Pull request #2951 by Jeremy Evans.
* Check Manifest.txt is up to date. Pull request #2953 by David Rodríguez.
* Clarify symlink conditionals in tests. Pull request #2962 by David
Rodríguez.
* Update command line parsing to work under ps. Pull request #2966 by
David Rodríguez.
* Properly test `Gem::Specifications.stub_for`. Pull request #2970 by
David Rodríguez.
* Fix Gem::LOADED_SPECS_MUTEX handling for recursive locking. Pull request
#2985 by MSP-Greg.
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/f5972338e0
|