| Age | Commit message (Collapse) | Author |
|
over lockfile method in Gemfile
It would be simpler to do `options[:lockfile] ||= ENV["BUNDLE_LOCKFILE"]`,
but that doesn't work as `options` is frozen.
Fixes https://github.com/ruby/rubygems/pull/9117
https://github.com/ruby/rubygems/commit/6e3603a0e9
|
|
This allows for specifying the lockfile to read and write. It mirrors
the --gemfile option, and has higher priority than the lockfile
method in the Gemfile. It also mirrors the bundle lock --lockfile
option.
When the --lockfile option is used, it is applied twice. First, before
the Gemfile is read, to specify the lockfile to operate on, and again
after the Gemfile is read, so that if the Gemfile has a lockfile
method that overrides the defintion's lockfile, the --lockfile option
still has higher precedence.
https://github.com/ruby/rubygems/commit/17acdd4a89
|
|
This specifies the lockfile location. This allows for easy support
of different lockfiles per Ruby version or platform.
https://github.com/ruby/rubygems/commit/b54d65bc0a
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
Co-authored-by: Colby Swandale <996377+colby-swandale@users.noreply.github.com>
|
|
This allows you to specify the lockfile to use. This is useful if
you want to use different lockfiles for different ruby versions or
platforms. You can also skip writing the lockfile by using a false
value.
https://github.com/ruby/rubygems/commit/2896aa3fc2
Co-authored-by: Colby Swandale <996377+colby-swandale@users.noreply.github.com>
|
|
https://github.com/rubygems/rubygems/commit/573ffad3ea
|
|
For synopsis, subcommand and flag documentation like other commands do.
https://github.com/rubygems/rubygems/commit/f528029756
|
|
There already different ways of toggling off this behavior, like setting
`bundle config clean false`, or configuring Bundler to install to system
gems with `bundle config path.system true`.
https://github.com/rubygems/rubygems/commit/6daa09f60a
|
|
https://github.com/rubygems/rubygems/commit/3e4687616a
|
|
BUNDLE_PATH are connected
https://github.com/rubygems/rubygems/commit/9ed20bddab
|
|
https://github.com/rubygems/rubygems/commit/591d2c0503
Notes:
Merged: https://github.com/ruby/ruby/pull/12840
|
|
We switched to nronn because ronn-ng felt abandoned, but it seems
it has activity again, so switch back.
Notes:
Merged: https://github.com/ruby/ruby/pull/12568
|
|
https://github.com/rubygems/rubygems/commit/8288cfd3e0
|
|
https://github.com/rubygems/rubygems/commit/506a863b36
|
|
Bundler always exits with a status code.
https://github.com/rubygems/rubygems/commit/3a38bd0b12
|
|
* Fix synopsis for mutually exclusive options.
* Add more descriptive examples.
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
https://github.com/rubygems/rubygems/commit/c0f1efda69
Co-authored-by: Jerome Dalbert <jerome.dalbert@gmail.com>
|
|
in Gemfile.lock
https://github.com/rubygems/rubygems/commit/0dd4bd59b4
|
|
https://github.com/rubygems/rubygems/commit/72103ca1e8
|
|
https://github.com/rubygems/rubygems/commit/9ee7069841
|
|
https://github.com/rubygems/rubygems/commit/e8a363713e
|
|
Also bring the man page up to date.
https://github.com/rubygems/rubygems/commit/a849bd6947
|
|
https://github.com/rubygems/rubygems/commit/e0ef515732
|
|
https://github.com/rubygems/rubygems/commit/55281f0eaa
|
|
If it's not there, when migrating to `nronn`, generated man page is
messed up.
https://github.com/rubygems/rubygems/commit/7161347648
|
|
bundle-install.1.ronn
https://github.com/rubygems/rubygems/commit/e956c5bbe4
|
|
value
`--keep-file-descriptors` is true by default.
https://github.com/rubygems/rubygems/commit/b28e88e228
|
|
(https://github.com/rubygems/rubygems/pull/6898)
Supports .tool-versions (ASDF) by checking for a line starting with "ruby"
before falling back to reading the entire file, as in .ruby-version.
https://github.com/rubygems/rubygems/commit/6c0a3e793a
|
|
https://github.com/rubygems/rubygems/commit/fb9354b7bf
|
|
https://github.com/rubygems/rubygems/commit/09ef74ef73
|
|
Co-Authored-By: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
|
|
to #windows?. (This is done instead of logging a deprecation warning.)
https://github.com/rubygems/rubygems/commit/b9fcc7c0ab
|
|
Pick from https://github.com/rubygems/rubygems/commit/e9304aed7e43308b99e70c2f7b92028315fee8a5
Notes:
Merged: https://github.com/ruby/ruby/pull/7345
|
|
There was an extra word ("with") in this sentence.
https://github.com/rubygems/rubygems/commit/ad3de5126c
|
|
https://github.com/rubygems/rubygems/commit/17037fe32c
Notes:
Merged: https://github.com/ruby/ruby/pull/6966
|
|
- Add mswin/mswin64 to platforms
- Use TruffleRuby as example instead of Rubinius
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
Co-authored-by: André Arko <andre@arko.net>
|
|
This behavior change was done in Bundler 2.2.0.
https://github.com/rubygems/bundler/pull/7142
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
https://github.com/rubygems/rubygems/commit/9510190be1
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6330
|
|
https://github.com/rubygems/rubygems/commit/16c3535413afebcdbab7582c6017c27b5da8a8dc
Notes:
Merged: https://github.com/ruby/ruby/pull/6326
|
|
https://github.com/rubygems/rubygems/commit/ab302f72c9
|
|
Specifying multiple primary sources in top-level was deprecated in
Bundler 1.13.
As Bundler CLI uses primary source instead of global, "global source"
is replaced with "primary source".
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
https://github.com/rubygems/rubygems/commit/1dd1753f6e
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6124
|
|
https://github.com/rubygems/rubygems/commit/b1826876d0
|
|
https://github.com/rubygems/rubygems/commit/3f83236c02
|
|
https://github.com/rubygems/rubygems/commit/08a0a5b7d1
|
|
consistent
Previously they had slightly different behavior when combined with
conservative updating flags.
The correct behavior is the `--update-strict` option, so `--script` now
does that, The `--update-strict` option is left there for now but I will
deprecate it later.
https://github.com/rubygems/rubygems/commit/ab42046229
|
|
https://github.com/rubygems/rubygems/commit/666f3cc724
|
|
Very often github source is used to temporarily use a modified gem
while a PR upstream is being reviewed.
So for instance https://github.com/ruby/bigdecimal/pull/211 will look like:
```ruby
gem "bigdecimal", github: "casperisfine/bigdecimal", branch: "git-gem" # https://github.com/ruby/bigdecimal/pull/200
```
It's annoying because you have to fiddle with the branch name, which is copied as `casperisfine:git-gem`, etc etc.
If I could simply use the PR URL like this:
```
gem "bigdecimal", github: "https://github.com/ruby/bigdecimal/pull/211"
```
It would make a very common task for me so much simpler.
https://github.com/rubygems/rubygems/commit/517c527751
|
|
https://github.com/rubygems/rubygems/commit/f328ef6f77
|
|
https://github.com/rubygems/rubygems/commit/58da501e5d
Notes:
Merged: https://github.com/ruby/ruby/pull/4789
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4533
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4383
|