| Age | Commit message (Collapse) | Author |
|---|
|
https://github.com/rubygems/rubygems/commit/573ffad3ea
|
|
For synopsis, subcommand and flag documentation like other commands do.
https://github.com/rubygems/rubygems/commit/f528029756
|
|
The `bundle list` command is a convenient way for human to know what gems and versions are available. By introducing a `--format=json` option, we can provide the same information to machines in a stable format that is robust to UI additions or modifications. It indirectly supports `Gemfile.lock` modifications by discouraging external tools from attempting to parse that format.
This addition allows for the scripting of installation tools, such as buildpacks, that wish to branch logic based on gem versions. For example:
```ruby
require "json"
command = "bundle list --format=json"
output = `#{command}`
raise "Command `#{command}` errored: #{output}" unless $?.success?
railties = JSON.parse(output).find {|gem| gem["name"] == railties }
if railties && Gem::Version.new(railties["version"]) >= Gem::Version.new("7")
puts "Using Rails greater than 7!"
end
```
The top level is an object with a single key, "gems", this structure allows us to add other information in the future (should we desire) without having to change the json schema.
https://github.com/rubygems/rubygems/commit/9e081b0689
|
|
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/commit/09ef74ef73
|
|
Co-Authored-By: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
|
|
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
|
|
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
|
|
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
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4143
|
|
55634a8af18a52df86c4275d70fa1179118bcc20
Notes:
Merged: https://github.com/ruby/ruby/pull/4021
|
