diff options
| author | The Bundler Bot <bot@bundler.io> | 2017-08-14 16:08:48 +0000 |
|---|---|---|
| committer | The Bundler Bot <bot@bundler.io> | 2017-08-14 16:08:48 +0000 |
| commit | a41379c5988a97716113f090bf972a71ef19b081 (patch) | |
| tree | cdcd9051eb7790cf6d53d53e9d5038e8a86c6ef4 /spec/bundler/shared_helpers_spec.rb | |
| parent | 605beb0a4800c923380f2dfe903f2fd2eee8b7c5 (diff) | |
| parent | 618c09b59d1318958c23b1b0031c68c93186851a (diff) | |
| download | bundler-a41379c5988a97716113f090bf972a71ef19b081.tar.gz | |
Auto merge of #5904 - bundler:seg-explicit-update-warning, r=indirect
[Update] Warn when an explicitly updated spec does not get a newer version
### What was the end-user problem that led to this PR?
The problem was you could run `bundle update foo bar` and it would be possible that either `foo` or `bar` not move to a newer version.
### What was your diagnosis of the problem?
My diagnosis was we should tell users when this happens!
### What is your fix for the problem, implemented in this PR?
My fix warns when a locked bundle has `bundle update` called with an explicit list of gems and one of those gems could not actually be _updated_.
### Why did you choose this fix out of the possible options?
I chose this fix because it didn't require mucking around with the resolved.
Diffstat (limited to 'spec/bundler/shared_helpers_spec.rb')
0 files changed, 0 insertions, 0 deletions