Age | Commit message (Collapse) | Author |
|
https://github.com/bundler/bundler/commit/be9d6e7cfc
|
|
Co-authored-by: Guillermo Guerrero <wolf.fox1985@gmail.com>
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
https://github.com/bundler/bundler/commit/4335df3e4c
|
|
It's the only usage of the `options_include_groups` attribute and its
name suggests a boolean, so it fits better now.
Co-authored-by: Guillermo Guerrero <wolf.fox1985@gmail.com>
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
https://github.com/bundler/bundler/commit/53c0fae760
|
|
Co-authored-by: Guillermo Guerrero <wolf.fox1985@gmail.com>
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
https://github.com/bundler/bundler/commit/832fb900f0
|
|
https://github.com/bundler/bundler/commit/69bee117fb
|
|
https://github.com/bundler/bundler/commit/5b285685a4
|
|
These specs are only run on bundler 2, so the compatibility method is
not needed.
https://github.com/bundler/bundler/commit/6cb28e3aeb
|
|
https://github.com/bundler/bundler/commit/8c83921d08
|
|
https://github.com/bundler/bundler/commit/04a04719f0
|
|
https://github.com/bundler/bundler/commit/1ee77d9c55
|
|
https://github.com/bundler/bundler/commit/ebcb25a3c3
|
|
https://github.com/bundler/bundler/commit/b5900e57a4
|
|
https://github.com/bundler/bundler/commit/344a881592
|
|
In these versions, the `approximate_recommendation` method doesn't
include the prerelease logic.
https://github.com/bundler/bundler/commit/caf13e9e4f
|
|
https://github.com/bundler/bundler/commit/9ddeeb1fe1
|
|
https://github.com/bundler/bundler/commit/72194d1aac
|
|
https://github.com/bundler/bundler/commit/50ccdb32c2
|
|
https://github.com/bundler/bundler/commit/1d017c3f36
|
|
https://github.com/bundler/bundler/commit/7ca4d4e83c
|
|
https://github.com/bundler/bundler/commit/2a44090cb6
|
|
https://github.com/bundler/bundler/commit/6d0a8f4128
|
|
https://github.com/bundler/bundler/commit/6d3b809695
|
|
It sounds like this was mistankenly added in
4337a499d0108fc3748084934aaed7591b355a26. Then the forgotten MANPATH key
was added in bf5bf106230772934602768bb31a68dc925691f0, but this one
should've been removed I think.
https://github.com/bundler/bundler/commit/a82ad111e5
|
|
https://github.com/bundler/bundler/commit/038f0d7c37
|
|
https://github.com/bundler/bundler/commit/3e5d4b2c42
|
|
PR 7248 incorrectly changed a path calculation. This reverts.
After running Azure Pipelines CI in my ruby/ruby fork and checking the 'bundler' jobs, the error was apparent...
https://github.com/bundler/bundler/commit/811755b413
|
|
https://github.com/bundler/bundler/commit/537c0ab712
|
|
@git_commit_sha not initialized'
https://github.com/bundler/bundler/commit/37a1eec8c8
|
|
https://github.com/bundler/bundler/commit/33892e1ed2
|
|
The additions of the `package` command are not actually backwards
incompatible, so we can do this transition without further care. All
existing specs of `bundle cache` pass when using the `bundle package`
implementation for it.
https://github.com/bundler/bundler/commit/69497adf90
|
|
So that we handle the removal of `bundle cache` just like we'll handle
the removal of `bundle show` and `bundle console`.
https://github.com/bundler/bundler/commit/ff1a669efb
|
|
Just change the default. The reason to do this is that the deprecation
message talks about the default being changed, not the option being
removed.
https://github.com/bundler/bundler/commit/eca1757792
|
|
https://github.com/bundler/bundler/commit/4df9edef95
|
|
This is inside a code branch where the condition is already met.
https://github.com/bundler/bundler/commit/8cdd6c37e6
|
|
https://github.com/bundler/bundler/commit/8ecd722b9f
|
|
It seems to pass under rubygems 2.5.2.
https://github.com/bundler/bundler/commit/062cd2be7c
|
|
Since it covers the whole range we support.
https://github.com/bundler/bundler/commit/c0b9d4e6c6
|
|
We plan to incrementally populate this array in rubygems, so that will
break the test because the first time `find_by_name("rack")` is called
will make the `rack` gem available in the array.
We can test the same thing using some other way, which is more
appropriate anyways, because `Bundler.rubygems.find_name` is only used
inside `bundler` to look for the `bundler` gem itself whereas
`Bundler.rubygems.all_specs` is used in more places.
https://github.com/bundler/bundler/commit/49c519ef47
|
|
The rubygems integration sets up a `post_reset` hook that resets the
specs back to what bundler knows after `Gem::Specification.reset` is
called (which is what `Gem.refresh` calls under the hood).
https://github.com/bundler/bundler/commit/3810f9945c
|
|
It contains a typo, so it can't be needed.
https://github.com/bundler/bundler/commit/ef38c97fbf
|
|
https://github.com/bundler/bundler/commit/98023e25de
|
|
Instead of setting the encoding globally, set it when reading the files.
https://github.com/bundler/bundler/commit/e2a5c45e4d
|
|
https://github.com/bundler/bundler/commit/e31880b1ea
|
|
https://github.com/bundler/bundler/commit/78608acf83
|
|
https://github.com/bundler/bundler/commit/3a2d2f0250
|
|
https://github.com/bundler/bundler/commit/52c5a0eede
|
|
https://github.com/bundler/bundler/commit/00b095b98f
|
|
https://github.com/bundler/bundler/commit/3dc509e645
|
|
https://github.com/bundler/bundler/commit/785c7af1f3
|
|
https://github.com/bundler/bundler/commit/60d720eb06
|