| Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/rubygems/commit/4c1eb2b274
|
|
As mentioned in https://github.com/ruby/rubygems/issues/9124,
the intent for changing the default command was to be more welcoming.
I think we can acheive that by attempting to install, but to print
that same help message if there is no Gemfile.
That should address both concerns.
https://github.com/ruby/rubygems/commit/f3f505c02a
|
|
https://github.com/ruby/rubygems/commit/f8fe7a5208
|
|
https://github.com/ruby/rubygems/commit/07f2daf51e
|
|
https://github.com/ruby/rubygems/commit/b237f759b0
|
|
https://github.com/ruby/rubygems/commit/3f5330c9fc
|
|
https://github.com/ruby/rubygems/commit/6e965b7872
|
|
https://github.com/ruby/rubygems/commit/bc77ec0bf2
|
|
https://github.com/rubygems/rubygems/commit/8078a747b3
|
|
|
|
provided snce Ruby 2.3
Notes:
Merged: https://github.com/ruby/ruby/pull/13311
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13275
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13275
|
|
https://github.com/rubygems/rubygems/commit/33c3caa63f
|
|
My application spends more than 30% of time during `bundle update`
comparing versions due to versions being sorted inside
next_package_to_try. This has been addressed in pub_grub by defining a
strategy interface (a `#next_package_and_version` method) which allows
consumers to have finer control over the heuristic to select the next
package to try.
This commit implements the new strategy interface to remove extraneous
version sorting (previously in next_package_to_try) since only the final
count of versions is used.
Combined with a previous change to pub_grub (already applied to
Bundler), this commit results in `bundle update` taking only half the
time it did on 2.6.5.
https://github.com/rubygems/rubygems/commit/62f69e27f0
|
|
https://github.com/rubygems/rubygems/commit/3aaa75e7b9
Notes:
Merged: https://github.com/ruby/ruby/pull/12968
|
|
https://github.com/rubygems/rubygems/commit/176dc7421c
Notes:
Merged: https://github.com/ruby/ruby/pull/12840
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
Notes:
Merged: https://github.com/ruby/ruby/pull/11860
|
|
It is loaded by `Fetcher` so in most case it's fine.
But if using `bundler/inline` and a gem need to be fetched,
`securerandom` will be loaded and cause a conflict.
Can be reproduced with:
```ruby
require 'bundler/inline'
gemfile do
source 'https://rubygems.org'
gem 'graphql', '~> 2.0'
gem 'graphql-client', '~> 0.18'
end
require 'json'
require 'graphql/client'
require 'graphql/client/http'
```
Ref: https://github.com/rails/rails/pull/52473#issuecomment-2284667451
Co-authored-by: Jean Boussier <jean.boussier@gmail.com>
|
|
https://github.com/rubygems/rubygems/commit/c38a96ceae
|
|
https://github.com/rubygems/rubygems/commit/5d6a8f2fb4
|
|
https://github.com/rubygems/rubygems/commit/62bc261042
|
|
|
|
Refactor vendoring to allow validating vendoring is reproducible
Helps ensure that unsuspecting diffs to the vendored code arent accidentally introduced
|
|
reproducible
Helps ensure that unsuspecting diffs to the vendored code arent accidentally introduced
https://github.com/rubygems/rubygems/commit/7c425d49dd
|
|
To match the versions that will be included in final ruby release.
https://github.com/rubygems/rubygems/commit/84394919fb
|
|
https://github.com/rubygems/rubygems/commit/cfc5018c54
|
|
https://github.com/rubygems/rubygems/commit/0d758e8926
|
|
See https://github.com/rails/thor/releases/tag/v1.3.0
https://github.com/rubygems/rubygems/commit/3c7165474b
|
|
https://github.com/rubygems/rubygems/commit/b0edf39083
|
|
|
|
Pick from https://github.com/rubygems/rubygems/commit/7a7b234721c375874b7e22b1c5b14925b943f04e
|
|
https://github.com/rubygems/rubygems/commit/d9a003b4e7
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/7462
|
|
Pick from https://github.com/rubygems/rubygems/commit/e9304aed7e43308b99e70c2f7b92028315fee8a5
Notes:
Merged: https://github.com/ruby/ruby/pull/7345
|
|
* Replaces the wording of "is forbidden" with "cannot be used"
* Fixes the method signature of VersionRange::Empty#eql?
https://github.com/rubygems/rubygems/commit/8c6b3f130b
Co-authored-by: Daniel Colson <danieljamescolson@gmail.com>
Notes:
Merged: https://github.com/ruby/ruby/pull/7345
|
|
We became a bit out of sync lately.
https://github.com/rubygems/rubygems/commit/6161a2610a
Notes:
Merged: https://github.com/ruby/ruby/pull/7345
|
|
from https://github.com/rubygems/rubygems/commit/0635c1423db5d7c461d53bf0c3329bca75de7609
Notes:
Merged: https://github.com/ruby/ruby/pull/7094
|
|
|
|
If the conflict explanation includes empty ranges and version unions,
Pub Grub was crashing.
https://github.com/rubygems/rubygems/commit/eb360b77a2
Notes:
Merged: https://github.com/ruby/ruby/pull/6966
|
|
https://github.com/rubygems/rubygems/commit/a8348d271d
Notes:
Merged: https://github.com/ruby/ruby/pull/6966
|