| Age | Commit message (Collapse) | Author |
|
I think they add unnecessary indirection and inconsistency to the specs.
https://github.com/rubygems/rubygems/commit/609924d985
|
|
It's always going to be either the first or the second platform in the
list so no need to keep an explicit list of all platforms.
https://github.com/rubygems/rubygems/commit/5d3cdb3855
|
|
https://github.com/rubygems/rubygems/commit/b48168bf1f
|
|
https://github.com/rubygems/rubygems/commit/d24c0c20e3
|
|
I don't think any supported platform has these names, so the mapping
should be unnecessary.
https://github.com/rubygems/rubygems/commit/6b1bdfc8a8
|
|
https://github.com/rubygems/rubygems/commit/639b970c64
|
|
https://github.com/rubygems/rubygems/commit/0e889ae7fb
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12624
|
|
https://github.com/rubygems/rubygems/commit/3df86cd9c6
|
|
https://github.com/rubygems/rubygems/commit/faaa594a4a
|
|
sinatra mock server
https://github.com/rubygems/rubygems/commit/0a168156d5
|
|
These changes were included when adding bundler plugin hooks for
`Bundler.require`, but they seem completely unrelated to that feature,
and have caused several issues.
https://github.com/rubygems/rubygems/commit/8d56551dcf
|
|
https://github.com/rubygems/rubygems/commit/0057382bb1
|
|
I think logger is only used to figure out which methods need to be made
noops in order to silence webrick during tests.
However, it seems possible to do the same using webrick's builtin logger
and the current method does not seem even correct since it's not
guaranteed that the logger gem and webrick's logger will use the same
methods.
Notes:
Merged: https://github.com/ruby/ruby/pull/12568
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12568
|
|
lockfile unless necessary
Even if they don't match the current Ruby version, they could still work
in other rubies. So it's better to keep them.
https://github.com/rubygems/rubygems/commit/9a3e583b0c
Notes:
Merged: https://github.com/ruby/ruby/pull/12568
|
|
https://github.com/rubygems/rubygems/commit/b73ee4059b
Notes:
Merged: https://github.com/ruby/ruby/pull/12568
|
|
directory on ruby 3.4
https://github.com/rubygems/rubygems/commit/027cdc750a
Notes:
Merged: https://github.com/ruby/ruby/pull/12568
|
|
I think we have consistent behavior regardless of the version of git
being used, and I'd like to keep it like that so I think we can remove
this filter.
https://github.com/rubygems/rubygems/commit/6a708128e9
Notes:
Merged: https://github.com/ruby/ruby/pull/12568
|
|
Can be reproduced, for example, with
```
bin/rspec spec/bundler/cli_spec.rb spec/other/cli_man_pages_spec.rb --order defined
```
https://github.com/rubygems/rubygems/commit/f57d199225
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12537
|
|
https://github.com/rubygems/rubygems/commit/5c6ca7a58c
|
|
https://github.com/rubygems/rubygems/commit/c8eeb0af9d
|
|
https://github.com/rubygems/rubygems/commit/eea07ad691
|
|
https://github.com/rubygems/rubygems/commit/809a2a17a7
|
|
https://github.com/rubygems/rubygems/commit/694d5f444e
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12469
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12452
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12444
|
|
installed
https://github.com/rubygems/rubygems/commit/a087c452ad
|
|
has been changed
Use Process.argv0 instead of $PROGRAM_NAME because $PROGRAM_NAME is
liable to be changed but Process.argv0 is not.
https://github.com/rubygems/rubygems/commit/43b747dc9e
|
|
https://github.com/rubygems/rubygems/commit/72316ed2fa
|
|
https://github.com/rubygems/rubygems/commit/77133a23f5
|
|
dependencies
https://github.com/rubygems/rubygems/commit/48fd2d0514
|
|
are documented
https://github.com/rubygems/rubygems/commit/20a834818b
|
|
licenses` commands
https://github.com/rubygems/rubygems/commit/6e1a515d58
|
|
Refactor to use real test cases rather than mock.
Add relative path tests wich `Dir.chdir`.
https://github.com/rubygems/rubygems/commit/ed556a0a53
|
|
files on Windows
https://github.com/rubygems/rubygems/commit/ed5b847f03
|
|
This is how Ruby works, and it's not going to change. So let's run the
test since it makes no sense to keep it pending.
https://github.com/rubygems/rubygems/commit/5f78d3c737
|
|
https://github.com/rubygems/rubygems/commit/abb658757f
|
|
They had slightly different behavior in Bundler 2 and Bundler 3 because
Bundler 3 will auto-clean after `bundle install`, so one of them system
installed gems won't be present when `Bundler.setup` fails.
We can unify the specs by moving installing system gems to _after_
`bundle install`, so the behavior in both cases is the same. Also, only
this spec actually needs these gems installed, so we can move that from
the `before` block to the body of the spec.
https://github.com/rubygems/rubygems/commit/b7251ec9c6
|
|
https://github.com/rubygems/rubygems/commit/9dbfce76cf
|
|
And make sure `bundle install --local` can install from it without git.
https://github.com/rubygems/rubygems/commit/7d6b631620
|
|
https://github.com/rubygems/rubygems/commit/23d06195fa
|
|
As long as some spec in the materialization is complete.
https://github.com/rubygems/rubygems/commit/9a673b0bbb
|
|
https://github.com/rubygems/rubygems/commit/0c3a65871a
|
|
https://github.com/rubygems/rubygems/commit/d8d68cc00e
|
|
to be conservative
When converging specification to pass the set of versions that should be
preserved from the lockfile during resolution, we should make sure all
top level gems are considered, and only exclude those gems themselves
(and not their dependencies) if their locked versions happen to not be
satisfied by an edited Gemfile.
https://github.com/rubygems/rubygems/commit/ed2f1b7b88
|
|
For consistency with other specs.
https://github.com/rubygems/rubygems/commit/a5b2449896
|
|
https://github.com/rubygems/rubygems/commit/c519830d4d
|