bundler 1.15.2 → 1.17.3

Sign up to get free protection for your applications and to get access to all the features.

Potentially problematic release.


This version of bundler might be problematic. Click here for more details.

Files changed (286) hide show
  1. checksums.yaml +5 -5
  2. data/CHANGELOG.md +302 -0
  3. data/README.md +17 -8
  4. data/bundler.gemspec +25 -9
  5. data/exe/bundle +1 -1
  6. data/exe/bundle_ruby +4 -3
  7. data/lib/bundler/build_metadata.rb +53 -0
  8. data/lib/bundler/capistrano.rb +5 -0
  9. data/lib/bundler/cli/add.rb +15 -6
  10. data/lib/bundler/cli/binstubs.rb +17 -9
  11. data/lib/bundler/cli/cache.rb +5 -4
  12. data/lib/bundler/cli/check.rb +3 -5
  13. data/lib/bundler/cli/clean.rb +5 -6
  14. data/lib/bundler/cli/common.rb +11 -2
  15. data/lib/bundler/cli/config.rb +2 -1
  16. data/lib/bundler/cli/console.rb +2 -1
  17. data/lib/bundler/cli/doctor.rb +48 -1
  18. data/lib/bundler/cli/exec.rb +6 -5
  19. data/lib/bundler/cli/gem.rb +13 -8
  20. data/lib/bundler/cli/info.rb +0 -1
  21. data/lib/bundler/cli/init.rb +18 -6
  22. data/lib/bundler/cli/inject.rb +1 -0
  23. data/lib/bundler/cli/install.rb +64 -61
  24. data/lib/bundler/cli/issue.rb +1 -1
  25. data/lib/bundler/cli/list.rb +58 -0
  26. data/lib/bundler/cli/lock.rb +0 -1
  27. data/lib/bundler/cli/open.rb +2 -2
  28. data/lib/bundler/cli/outdated.rb +20 -9
  29. data/lib/bundler/cli/package.rb +9 -6
  30. data/lib/bundler/cli/platform.rb +1 -0
  31. data/lib/bundler/cli/plugin.rb +1 -0
  32. data/lib/bundler/cli/pristine.rb +20 -6
  33. data/lib/bundler/cli/remove.rb +18 -0
  34. data/lib/bundler/cli/show.rb +0 -1
  35. data/lib/bundler/cli/update.rb +35 -7
  36. data/lib/bundler/cli/viz.rb +1 -0
  37. data/lib/bundler/cli.rb +227 -89
  38. data/lib/bundler/compact_index_client/cache.rb +1 -2
  39. data/lib/bundler/compact_index_client/updater.rb +14 -4
  40. data/lib/bundler/compact_index_client.rb +1 -0
  41. data/lib/bundler/compatibility_guard.rb +14 -0
  42. data/lib/bundler/constants.rb +1 -0
  43. data/lib/bundler/current_ruby.rb +13 -5
  44. data/lib/bundler/definition.rb +192 -139
  45. data/lib/bundler/dep_proxy.rb +3 -1
  46. data/lib/bundler/dependency.rb +9 -9
  47. data/lib/bundler/deployment.rb +1 -1
  48. data/lib/bundler/deprecate.rb +15 -3
  49. data/lib/bundler/dsl.rb +115 -64
  50. data/lib/bundler/endpoint_specification.rb +10 -1
  51. data/lib/bundler/env.rb +90 -29
  52. data/lib/bundler/environment_preserver.rb +27 -6
  53. data/lib/bundler/errors.rb +1 -0
  54. data/lib/bundler/feature_flag.rb +46 -4
  55. data/lib/bundler/fetcher/base.rb +1 -0
  56. data/lib/bundler/fetcher/compact_index.rb +2 -11
  57. data/lib/bundler/fetcher/dependency.rb +2 -1
  58. data/lib/bundler/fetcher/downloader.rb +11 -5
  59. data/lib/bundler/fetcher/index.rb +3 -2
  60. data/lib/bundler/fetcher.rb +18 -11
  61. data/lib/bundler/friendly_errors.rb +6 -1
  62. data/lib/bundler/gem_helper.rb +19 -10
  63. data/lib/bundler/gem_helpers.rb +1 -0
  64. data/lib/bundler/gem_remote_fetcher.rb +1 -0
  65. data/lib/bundler/gem_tasks.rb +1 -0
  66. data/lib/bundler/gem_version_promoter.rb +17 -2
  67. data/lib/bundler/gemdeps.rb +1 -0
  68. data/lib/bundler/graph.rb +1 -0
  69. data/lib/bundler/index.rb +8 -8
  70. data/lib/bundler/injector.rb +192 -30
  71. data/lib/bundler/inline.rb +5 -7
  72. data/lib/bundler/installer/gem_installer.rb +11 -2
  73. data/lib/bundler/installer/parallel_installer.rb +78 -42
  74. data/lib/bundler/installer/standalone.rb +1 -0
  75. data/lib/bundler/installer.rb +138 -53
  76. data/lib/bundler/lazy_specification.rb +3 -2
  77. data/lib/bundler/lockfile_generator.rb +95 -0
  78. data/lib/bundler/lockfile_parser.rb +10 -4
  79. data/lib/bundler/match_platform.rb +1 -0
  80. data/lib/bundler/mirror.rb +8 -5
  81. data/lib/bundler/plugin/api/source.rb +9 -2
  82. data/lib/bundler/plugin/events.rb +61 -0
  83. data/lib/bundler/plugin/index.rb +7 -2
  84. data/lib/bundler/plugin/installer.rb +7 -6
  85. data/lib/bundler/plugin/source_list.rb +7 -8
  86. data/lib/bundler/plugin.rb +13 -5
  87. data/lib/bundler/process_lock.rb +24 -0
  88. data/lib/bundler/psyched_yaml.rb +10 -0
  89. data/lib/bundler/remote_specification.rb +1 -0
  90. data/lib/bundler/resolver/spec_group.rb +106 -0
  91. data/lib/bundler/resolver.rb +158 -195
  92. data/lib/bundler/retry.rb +1 -0
  93. data/lib/bundler/ruby_dsl.rb +1 -0
  94. data/lib/bundler/ruby_version.rb +2 -1
  95. data/lib/bundler/rubygems_ext.rb +5 -4
  96. data/lib/bundler/rubygems_gem_installer.rb +31 -1
  97. data/lib/bundler/rubygems_integration.rb +71 -32
  98. data/lib/bundler/runtime.rb +11 -9
  99. data/lib/bundler/settings/validator.rb +102 -0
  100. data/lib/bundler/settings.rb +200 -77
  101. data/lib/bundler/setup.rb +1 -0
  102. data/lib/bundler/shared_helpers.rb +131 -26
  103. data/lib/bundler/similarity_detector.rb +1 -0
  104. data/lib/bundler/source/gemspec.rb +1 -0
  105. data/lib/bundler/source/git/git_proxy.rb +21 -11
  106. data/lib/bundler/source/git.rb +24 -19
  107. data/lib/bundler/source/metadata.rb +62 -0
  108. data/lib/bundler/source/path/installer.rb +2 -0
  109. data/lib/bundler/source/path.rb +8 -8
  110. data/lib/bundler/source/rubygems/remote.rb +8 -2
  111. data/lib/bundler/source/rubygems.rb +161 -84
  112. data/lib/bundler/source.rb +36 -0
  113. data/lib/bundler/source_list.rb +75 -15
  114. data/lib/bundler/spec_set.rb +10 -5
  115. data/lib/bundler/ssl_certs/certificate_manager.rb +2 -1
  116. data/lib/bundler/stub_specification.rb +1 -0
  117. data/lib/bundler/templates/.document +1 -0
  118. data/lib/bundler/templates/Executable +12 -0
  119. data/lib/bundler/templates/Executable.bundler +105 -0
  120. data/lib/bundler/templates/Gemfile +1 -0
  121. data/lib/bundler/templates/gems.rb +8 -0
  122. data/lib/bundler/templates/newgem/README.md.tt +1 -1
  123. data/lib/bundler/templates/newgem/gitignore.tt +0 -1
  124. data/lib/bundler/templates/newgem/lib/newgem.rb.tt +1 -0
  125. data/lib/bundler/templates/newgem/newgem.gemspec.tt +12 -3
  126. data/lib/bundler/templates/newgem/rspec.tt +1 -0
  127. data/lib/bundler/templates/newgem/spec/newgem_spec.rb.tt +0 -2
  128. data/lib/bundler/templates/newgem/{.travis.yml.tt → travis.yml.tt} +2 -0
  129. data/lib/bundler/ui/rg_proxy.rb +1 -0
  130. data/lib/bundler/ui/shell.rb +17 -4
  131. data/lib/bundler/ui/silent.rb +1 -0
  132. data/lib/bundler/ui.rb +1 -0
  133. data/lib/bundler/uri_credentials_filter.rb +1 -0
  134. data/lib/bundler/vendor/fileutils/lib/fileutils.rb +1638 -0
  135. data/lib/bundler/vendor/molinillo/lib/molinillo/compatibility.rb +26 -0
  136. data/lib/bundler/vendor/molinillo/lib/molinillo/delegates/resolution_state.rb +7 -0
  137. data/lib/bundler/vendor/molinillo/lib/molinillo/delegates/specification_provider.rb +1 -0
  138. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/action.rb +1 -0
  139. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/add_edge_no_circular.rb +1 -0
  140. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/add_vertex.rb +1 -0
  141. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/delete_edge.rb +1 -0
  142. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/detach_vertex_named.rb +1 -0
  143. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/log.rb +1 -0
  144. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/set_payload.rb +1 -0
  145. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/tag.rb +1 -0
  146. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph/vertex.rb +15 -4
  147. data/lib/bundler/vendor/molinillo/lib/molinillo/dependency_graph.rb +3 -2
  148. data/lib/bundler/vendor/molinillo/lib/molinillo/errors.rb +75 -7
  149. data/lib/bundler/vendor/molinillo/lib/molinillo/gem_metadata.rb +2 -1
  150. data/lib/bundler/vendor/molinillo/lib/molinillo/modules/specification_provider.rb +1 -0
  151. data/lib/bundler/vendor/molinillo/lib/molinillo/modules/ui.rb +3 -1
  152. data/lib/bundler/vendor/molinillo/lib/molinillo/resolution.rb +491 -148
  153. data/lib/bundler/vendor/molinillo/lib/molinillo/resolver.rb +1 -0
  154. data/lib/bundler/vendor/molinillo/lib/molinillo/state.rb +8 -4
  155. data/lib/bundler/vendor/molinillo/lib/molinillo.rb +2 -0
  156. data/lib/bundler/vendor/net-http-persistent/lib/net/http/persistent.rb +1 -1
  157. data/lib/bundler/vendor/thor/lib/thor/actions/create_file.rb +1 -0
  158. data/lib/bundler/vendor/thor/lib/thor/actions/create_link.rb +1 -0
  159. data/lib/bundler/vendor/thor/lib/thor/actions/empty_directory.rb +9 -1
  160. data/lib/bundler/vendor/thor/lib/thor/actions/file_manipulation.rb +45 -8
  161. data/lib/bundler/vendor/thor/lib/thor/actions/inject_into_file.rb +9 -3
  162. data/lib/bundler/vendor/thor/lib/thor/actions.rb +6 -3
  163. data/lib/bundler/vendor/thor/lib/thor/base.rb +27 -4
  164. data/lib/bundler/vendor/thor/lib/thor/command.rb +9 -7
  165. data/lib/bundler/vendor/thor/lib/thor/core_ext/hash_with_indifferent_access.rb +12 -0
  166. data/lib/bundler/vendor/thor/lib/thor/group.rb +1 -1
  167. data/lib/bundler/vendor/thor/lib/thor/line_editor/basic.rb +2 -0
  168. data/lib/bundler/vendor/thor/lib/thor/parser/option.rb +5 -5
  169. data/lib/bundler/vendor/thor/lib/thor/parser/options.rb +6 -5
  170. data/lib/bundler/vendor/thor/lib/thor/runner.rb +6 -4
  171. data/lib/bundler/vendor/thor/lib/thor/shell/basic.rb +10 -9
  172. data/lib/bundler/vendor/thor/lib/thor/version.rb +1 -1
  173. data/lib/bundler/vendor/thor/lib/thor.rb +25 -8
  174. data/lib/bundler/vendored_fileutils.rb +9 -0
  175. data/lib/bundler/vendored_molinillo.rb +1 -0
  176. data/lib/bundler/vendored_persistent.rb +35 -0
  177. data/lib/bundler/vendored_thor.rb +1 -0
  178. data/lib/bundler/version.rb +6 -2
  179. data/lib/bundler/version_ranges.rb +1 -0
  180. data/lib/bundler/vlad.rb +5 -0
  181. data/lib/bundler/worker.rb +1 -0
  182. data/lib/bundler/yaml_serializer.rb +3 -3
  183. data/lib/bundler.rb +86 -52
  184. data/man/bundle-add.1 +18 -3
  185. data/man/bundle-add.1.txt +26 -14
  186. data/man/bundle-add.ronn +13 -2
  187. data/man/bundle-binstubs.1 +11 -1
  188. data/man/bundle-binstubs.1.txt +33 -18
  189. data/man/bundle-binstubs.ronn +15 -1
  190. data/man/bundle-check.1 +4 -4
  191. data/man/bundle-check.1.txt +15 -14
  192. data/man/bundle-check.ronn +3 -3
  193. data/man/bundle-clean.1 +1 -1
  194. data/man/bundle-clean.1.txt +10 -10
  195. data/man/bundle-config.1 +129 -29
  196. data/man/bundle-config.1.txt +285 -174
  197. data/man/bundle-config.ronn +167 -88
  198. data/man/bundle-doctor.1 +44 -0
  199. data/man/bundle-doctor.1.txt +44 -0
  200. data/man/bundle-doctor.ronn +33 -0
  201. data/man/bundle-exec.1 +6 -3
  202. data/man/bundle-exec.1.txt +78 -71
  203. data/man/bundle-exec.ronn +10 -3
  204. data/man/bundle-gem.1 +3 -3
  205. data/man/bundle-gem.1.txt +40 -39
  206. data/man/bundle-gem.ronn +2 -1
  207. data/man/bundle-info.1 +1 -1
  208. data/man/bundle-info.1.txt +8 -8
  209. data/man/bundle-init.1 +9 -4
  210. data/man/bundle-init.1.txt +23 -13
  211. data/man/bundle-init.ronn +15 -4
  212. data/man/bundle-inject.1 +4 -4
  213. data/man/bundle-inject.1.txt +10 -10
  214. data/man/bundle-inject.ronn +3 -3
  215. data/man/bundle-install.1 +31 -28
  216. data/man/bundle-install.1.txt +205 -194
  217. data/man/bundle-install.ronn +44 -35
  218. data/man/bundle-list.1 +50 -0
  219. data/man/bundle-list.1.txt +43 -0
  220. data/man/bundle-list.ronn +33 -0
  221. data/man/bundle-lock.1 +1 -1
  222. data/man/bundle-lock.1.txt +47 -47
  223. data/man/bundle-lock.ronn +1 -1
  224. data/man/bundle-open.1 +1 -1
  225. data/man/bundle-open.1.txt +7 -7
  226. data/man/bundle-outdated.1 +7 -3
  227. data/man/bundle-outdated.1.txt +40 -36
  228. data/man/bundle-outdated.ronn +6 -2
  229. data/man/bundle-package.1 +6 -3
  230. data/man/bundle-package.1.txt +44 -39
  231. data/man/bundle-package.ronn +7 -2
  232. data/man/bundle-platform.1 +1 -1
  233. data/man/bundle-platform.1.txt +13 -13
  234. data/man/bundle-pristine.1 +21 -3
  235. data/man/bundle-pristine.1.txt +33 -10
  236. data/man/bundle-pristine.ronn +24 -3
  237. data/man/bundle-remove.1 +31 -0
  238. data/man/bundle-remove.1.txt +34 -0
  239. data/man/bundle-remove.ronn +23 -0
  240. data/man/bundle-show.1 +3 -3
  241. data/man/bundle-show.1.txt +14 -12
  242. data/man/bundle-show.ronn +3 -2
  243. data/man/bundle-update.1 +13 -9
  244. data/man/bundle-update.1.txt +133 -130
  245. data/man/bundle-update.ronn +21 -17
  246. data/man/bundle-viz.1 +7 -7
  247. data/man/bundle-viz.1.txt +17 -15
  248. data/man/bundle-viz.ronn +6 -6
  249. data/man/bundle.1 +31 -23
  250. data/man/bundle.1.txt +63 -57
  251. data/man/bundle.ronn +35 -29
  252. data/man/gemfile.5 +44 -8
  253. data/man/gemfile.5.ronn +54 -8
  254. data/man/gemfile.5.txt +218 -165
  255. data/man/index.txt +25 -15
  256. metadata +36 -36
  257. data/.codeclimate.yml +0 -25
  258. data/.gitignore +0 -18
  259. data/.rspec +0 -3
  260. data/.rubocop.yml +0 -131
  261. data/.rubocop_todo.yml +0 -418
  262. data/.travis.yml +0 -122
  263. data/CODE_OF_CONDUCT.md +0 -42
  264. data/CONTRIBUTING.md +0 -17
  265. data/Rakefile +0 -338
  266. data/bin/rake +0 -19
  267. data/bin/rspec +0 -15
  268. data/bin/rubocop +0 -17
  269. data/bin/with_rubygems +0 -39
  270. data/doc/README.md +0 -30
  271. data/doc/TROUBLESHOOTING.md +0 -64
  272. data/doc/contributing/BUG_TRIAGE.md +0 -36
  273. data/doc/contributing/COMMUNITY.md +0 -13
  274. data/doc/contributing/GETTING_HELP.md +0 -11
  275. data/doc/contributing/HOW_YOU_CAN_HELP.md +0 -27
  276. data/doc/contributing/ISSUES.md +0 -51
  277. data/doc/contributing/README.md +0 -38
  278. data/doc/development/NEW_FEATURES.md +0 -10
  279. data/doc/development/PULL_REQUESTS.md +0 -40
  280. data/doc/development/README.md +0 -19
  281. data/doc/development/RELEASING.md +0 -9
  282. data/doc/development/SETUP.md +0 -27
  283. data/doc/documentation/README.md +0 -29
  284. data/doc/documentation/VISION.md +0 -26
  285. data/doc/documentation/WRITING.md +0 -54
  286. data/task/release.rake +0 -116
data/man/bundle-show.1 CHANGED
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "BUNDLE\-SHOW" "1" "June 2017" "" ""
4
+ .TH "BUNDLE\-SHOW" "1" "November 2018" "" ""
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBbundle\-show\fR \- Shows all the gems in your bundle, or the path to a gem
@@ -10,7 +10,7 @@
10
10
  \fBbundle show\fR [GEM] [\-\-paths]
11
11
  .
12
12
  .SH "DESCRIPTION"
13
- Without the [GEM] option, \fBshow\fR will print a list of the names and versions of all gems that are required by your \fBGemfile(5)\fR\.
13
+ Without the [GEM] option, \fBshow\fR will print a list of the names and versions of all gems that are required by your [\fBGemfile(5)\fR][Gemfile(5)], sorted by name\.
14
14
  .
15
15
  .P
16
16
  Calling show with [GEM] will list the exact location of that gem on your machine\.
@@ -19,5 +19,5 @@ Calling show with [GEM] will list the exact location of that gem on your machine
19
19
  .
20
20
  .TP
21
21
  \fB\-\-paths\fR
22
- List the paths of all gems that are required by your \fBGemfile(5)\fR\.
22
+ List the paths of all gems that are required by your [\fBGemfile(5)\fR][Gemfile(5)], sorted by gem name\.
23
23
 
@@ -2,24 +2,26 @@ BUNDLE-SHOW(1) BUNDLE-SHOW(1)
2
2
 
3
3
 
4
4
 
5
- 1mNAME0m
6
- 1mbundle-show 22m- Shows all the gems in your bundle, or the path to a gem
5
+ NAME
6
+ bundle-show - Shows all the gems in your bundle, or the path to a gem
7
7
 
8
- 1mSYNOPSIS0m
9
- 1mbundle show 22m[GEM] [--paths]
8
+ SYNOPSIS
9
+ bundle show [GEM] [--paths]
10
10
 
11
- 1mDESCRIPTION0m
12
- Without the [GEM] option, 1mshow 22mwill print a list of the names and ver-
13
- sions of all gems that are required by your 1mGemfile(5)22m.
11
+ DESCRIPTION
12
+ Without the [GEM] option, show will print a list of the names and ver-
13
+ sions of all gems that are required by your [Gemfile(5)][Gemfile(5)],
14
+ sorted by name.
14
15
 
15
- Calling show with [GEM] will list the exact location of that gem on
16
+ Calling show with [GEM] will list the exact location of that gem on
16
17
  your machine.
17
18
 
18
- 1mOPTIONS0m
19
- 1m--paths0m
20
- List the paths of all gems that are required by your 1mGemfile(5)22m.
19
+ OPTIONS
20
+ --paths
21
+ List the paths of all gems that are required by your [Gem-
22
+ file(5)][Gemfile(5)], sorted by gem name.
21
23
 
22
24
 
23
25
 
24
26
 
25
- June 2017 BUNDLE-SHOW(1)
27
+ November 2018 BUNDLE-SHOW(1)
data/man/bundle-show.ronn CHANGED
@@ -9,7 +9,7 @@ bundle-show(1) -- Shows all the gems in your bundle, or the path to a gem
9
9
  ## DESCRIPTION
10
10
 
11
11
  Without the [GEM] option, `show` will print a list of the names and versions of
12
- all gems that are required by your `Gemfile(5)`.
12
+ all gems that are required by your [`Gemfile(5)`][Gemfile(5)], sorted by name.
13
13
 
14
14
  Calling show with [GEM] will list the exact location of that gem on your
15
15
  machine.
@@ -17,4 +17,5 @@ machine.
17
17
  ## OPTIONS
18
18
 
19
19
  * `--paths`:
20
- List the paths of all gems that are required by your `Gemfile(5)`.
20
+ List the paths of all gems that are required by your [`Gemfile(5)`][Gemfile(5)],
21
+ sorted by gem name.
data/man/bundle-update.1 CHANGED
@@ -1,16 +1,16 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "BUNDLE\-UPDATE" "1" "June 2017" "" ""
4
+ .TH "BUNDLE\-UPDATE" "1" "December 2018" "" ""
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBbundle\-update\fR \- Update your gems to the latest available versions
8
8
  .
9
9
  .SH "SYNOPSIS"
10
- \fBbundle update\fR \fI*gems\fR [\-\-group=NAME] [\-\-source=NAME] [\-\-local] [\-\-ruby] [\-\-bundler[=VERSION]] [\-\-full\-index] [\-\-jobs=JOBS] [\-\-quiet] [\-\-force] [\-\-patch|\-\-minor|\-\-major] [\-\-strict] [\-\-conservative]
10
+ \fBbundle update\fR \fI*gems\fR [\-\-all] [\-\-group=NAME] [\-\-source=NAME] [\-\-local] [\-\-ruby] [\-\-bundler[=VERSION]] [\-\-full\-index] [\-\-jobs=JOBS] [\-\-quiet] [\-\-force] [\-\-patch|\-\-minor|\-\-major] [\-\-strict] [\-\-conservative]
11
11
  .
12
12
  .SH "DESCRIPTION"
13
- Update the gems specified (all gems, if none are specified), ignoring the previously installed gems specified in the \fBGemfile\.lock\fR\. In general, you should use bundle install(1) \fIbundle\-install\.1\.html\fR to install the same exact gems and versions across machines\.
13
+ Update the gems specified (all gems, if \fB\-\-all\fR flag is used), ignoring the previously installed gems specified in the \fBGemfile\.lock\fR\. In general, you should use bundle install(1) \fIbundle\-install\.1\.html\fR to install the same exact gems and versions across machines\.
14
14
  .
15
15
  .P
16
16
  You would use \fBbundle update\fR to explicitly update the version of a gem\.
@@ -18,7 +18,11 @@ You would use \fBbundle update\fR to explicitly update the version of a gem\.
18
18
  .SH "OPTIONS"
19
19
  .
20
20
  .TP
21
- \fB\-\-group=<name>\fR
21
+ \fB\-\-all\fR
22
+ Update all gems specified in Gemfile\.
23
+ .
24
+ .TP
25
+ \fB\-\-group=<name>\fR, \fB\-g=[<name>]\fR
22
26
  Only update the gems in the specified group\. For instance, you can update all gems in the development group with \fBbundle update \-\-group development\fR\. You can also call \fBbundle update rails \-\-group test\fR to update the rails gem and all gems in the test group, for example\.
23
27
  .
24
28
  .TP
@@ -42,7 +46,7 @@ Update the locked version of bundler to the invoked bundler version\.
42
46
  Fall back to using the single\-file index of all gems\.
43
47
  .
44
48
  .TP
45
- \fB\-\-jobs=[<number>]\fR
49
+ \fB\-\-jobs=[<number>]\fR, \fB\-j[<number>]\fR
46
50
  Specify the number of jobs to run in parallel\. The default is \fB1\fR\.
47
51
  .
48
52
  .TP
@@ -55,7 +59,7 @@ Only output warnings and errors\.
55
59
  .
56
60
  .TP
57
61
  \fB\-\-force\fR
58
- Force downloading every gem\.
62
+ Force downloading every gem\. \fB\-\-redownload\fR is an alias of this option\.
59
63
  .
60
64
  .TP
61
65
  \fB\-\-patch\fR
@@ -78,7 +82,7 @@ Do not allow any gem to be updated past latest \fB\-\-patch\fR | \fB\-\-minor\fR
78
82
  Use bundle install conservative update behavior and do not allow shared dependencies to be updated\.
79
83
  .
80
84
  .SH "UPDATING ALL GEMS"
81
- If you run \fBbundle update\fR with no parameters, bundler will ignore any previously installed gems and resolve all dependencies again based on the latest versions of all gems available in the sources\.
85
+ If you run \fBbundle update \-\-all\fR, bundler will ignore any previously installed gems and resolve all dependencies again based on the latest versions of all gems available in the sources\.
82
86
  .
83
87
  .P
84
88
  Consider the following Gemfile(5):
@@ -149,7 +153,7 @@ After checking in the \fBGemfile\.lock\fR into version control and cloning it on
149
153
  However, from time to time, you might want to update the gems you are using to the newest versions that still match the gems in your Gemfile(5)\.
150
154
  .
151
155
  .P
152
- To do this, run \fBbundle update\fR, which will ignore the \fBGemfile\.lock\fR, and resolve all the dependencies again\. Keep in mind that this process can result in a significantly different set of the 25 gems, based on the requirements of new gems that the gem authors released since the last time you ran \fBbundle update\fR\.
156
+ To do this, run \fBbundle update \-\-all\fR, which will ignore the \fBGemfile\.lock\fR, and resolve all the dependencies again\. Keep in mind that this process can result in a significantly different set of the 25 gems, based on the requirements of new gems that the gem authors released since the last time you ran \fBbundle update \-\-all\fR\.
153
157
  .
154
158
  .SH "UPDATING A LIST OF GEMS"
155
159
  Sometimes, you want to update a single gem in the Gemfile(5), and leave the rest of the gems that you specified locked to the versions in the \fBGemfile\.lock\fR\.
@@ -384,7 +388,7 @@ $ bundle update rails thin
384
388
  If you want to update all the gems to the latest possible versions that still match the gems listed in the Gemfile(5), run
385
389
  .
386
390
  .IP
387
- $ bundle update
391
+ $ bundle update \-\-all
388
392
  .
389
393
  .IP "" 0
390
394
 
@@ -2,83 +2,86 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
2
2
 
3
3
 
4
4
 
5
- 1mNAME0m
6
- 1mbundle-update 22m- Update your gems to the latest available versions
7
-
8
- 1mSYNOPSIS0m
9
- 1mbundle update 4m22m*gems24m [--group=NAME] [--source=NAME] [--local] [--ruby]
10
- [--bundler[=VERSION]] [--full-index] [--jobs=JOBS] [--quiet] [--force]
11
- [--patch|--minor|--major] [--strict] [--conservative]
12
-
13
- 1mDESCRIPTION0m
14
- Update the gems specified (all gems, if none are specified), ignoring
15
- the previously installed gems specified in the 1mGemfile.lock22m. In gen-
16
- eral, you should use bundle install(1) 4mbundle-install.1.html24m to install
5
+ NAME
6
+ bundle-update - Update your gems to the latest available versions
7
+
8
+ SYNOPSIS
9
+ bundle update *gems [--all] [--group=NAME] [--source=NAME] [--local]
10
+ [--ruby] [--bundler[=VERSION]] [--full-index] [--jobs=JOBS] [--quiet]
11
+ [--force] [--patch|--minor|--major] [--strict] [--conservative]
12
+
13
+ DESCRIPTION
14
+ Update the gems specified (all gems, if --all flag is used), ignoring
15
+ the previously installed gems specified in the Gemfile.lock. In gen-
16
+ eral, you should use bundle install(1) bundle-install.1.html to install
17
17
  the same exact gems and versions across machines.
18
18
 
19
- You would use 1mbundle update 22mto explicitly update the version of a gem.
19
+ You would use bundle update to explicitly update the version of a gem.
20
20
 
21
- 1mOPTIONS0m
22
- 1m--group=<name>0m
23
- Only update the gems in the specified group. For instance, you
24
- can update all gems in the development group with 1mbundle update0m
25
- 1m--group development22m. You can also call 1mbundle update rails0m
26
- 1m--group test 22mto update the rails gem and all gems in the test
21
+ OPTIONS
22
+ --all Update all gems specified in Gemfile.
23
+
24
+ --group=<name>, -g=[<name>]
25
+ Only update the gems in the specified group. For instance, you
26
+ can update all gems in the development group with bundle update
27
+ --group development. You can also call bundle update rails
28
+ --group test to update the rails gem and all gems in the test
27
29
  group, for example.
28
30
 
29
- 1m--source=<name>0m
30
- The name of a 1m:git 22mor 1m:path 22msource used in the Gemfile(5). For
31
- instance, with a 1m:git 22msource of
32
- 1mhttp://github.com/rails/rails.git22m, you would call 1mbundle update0m
33
- 1m--source rails0m
31
+ --source=<name>
32
+ The name of a :git or :path source used in the Gemfile(5). For
33
+ instance, with a :git source of
34
+ http://github.com/rails/rails.git, you would call bundle update
35
+ --source rails
34
36
 
35
- 1m--local0m
36
- Do not attempt to fetch gems remotely and use the gem cache
37
+ --local
38
+ Do not attempt to fetch gems remotely and use the gem cache
37
39
  instead.
38
40
 
39
- 1m--ruby 22mUpdate the locked version of Ruby to the current version of
41
+ --ruby Update the locked version of Ruby to the current version of
40
42
  Ruby.
41
43
 
42
- 1m--bundler0m
44
+ --bundler
43
45
  Update the locked version of bundler to the invoked bundler ver-
44
46
  sion.
45
47
 
46
- 1m--full-index0m
48
+ --full-index
47
49
  Fall back to using the single-file index of all gems.
48
50
 
49
- 1m--jobs=[<number>]0m
50
- Specify the number of jobs to run in parallel. The default is 1m122m.
51
+ --jobs=[<number>], -j[<number>]
52
+ Specify the number of jobs to run in parallel. The default is 1.
51
53
 
52
- 1m--retry=[<number>]0m
53
- Retry failed network or git requests for 4mnumber24m times.
54
+ --retry=[<number>]
55
+ Retry failed network or git requests for number times.
54
56
 
55
- 1m--quiet0m
57
+ --quiet
56
58
  Only output warnings and errors.
57
59
 
58
- 1m--force0m
59
- Force downloading every gem.
60
+ --force
61
+ Force downloading every gem. --redownload is an alias of this
62
+ option.
60
63
 
61
- 1m--patch0m
64
+ --patch
62
65
  Prefer updating only to next patch version.
63
66
 
64
- 1m--minor0m
67
+ --minor
65
68
  Prefer updating only to next minor version.
66
69
 
67
- 1m--major0m
70
+ --major
68
71
  Prefer updating to next major version (default).
69
72
 
70
- 1m--strict0m
71
- Do not allow any gem to be updated past latest 1m--patch 22m| 1m--minor0m
72
- | 1m--major22m.
73
+ --strict
74
+ Do not allow any gem to be updated past latest --patch | --minor
75
+ | --major.
73
76
 
74
- 1m--conservative0m
77
+ --conservative
75
78
  Use bundle install conservative update behavior and do not allow
76
79
  shared dependencies to be updated.
77
80
 
78
- 1mUPDATING ALL GEMS0m
79
- If you run 1mbundle update 22mwith no parameters, bundler will ignore any
80
- previously installed gems and resolve all dependencies again based on
81
- the latest versions of all gems available in the sources.
81
+ UPDATING ALL GEMS
82
+ If you run bundle update --all, bundler will ignore any previously
83
+ installed gems and resolve all dependencies again based on the latest
84
+ versions of all gems available in the sources.
82
85
 
83
86
  Consider the following Gemfile(5):
84
87
 
@@ -91,8 +94,8 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
91
94
 
92
95
 
93
96
 
94
- When you run bundle install(1) 4mbundle-install.1.html24m the first time,
95
- bundler will resolve all of the dependencies, all the way down, and
97
+ When you run bundle install(1) bundle-install.1.html the first time,
98
+ bundler will resolve all of the dependencies, all the way down, and
96
99
  install what you need:
97
100
 
98
101
 
@@ -131,44 +134,44 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
131
134
 
132
135
 
133
136
 
134
- As you can see, even though you have two gems in the Gemfile(5), your
135
- application needs 26 different gems in order to run. Bundler remembers
136
- the exact versions it installed in 1mGemfile.lock22m. The next time you run
137
- bundle install(1) 4mbundle-install.1.html24m, bundler skips the dependency
137
+ As you can see, even though you have two gems in the Gemfile(5), your
138
+ application needs 26 different gems in order to run. Bundler remembers
139
+ the exact versions it installed in Gemfile.lock. The next time you run
140
+ bundle install(1) bundle-install.1.html, bundler skips the dependency
138
141
  resolution and installs the same gems as it installed last time.
139
142
 
140
- After checking in the 1mGemfile.lock 22minto version control and cloning it
141
- on another machine, running bundle install(1) 4mbundle-install.1.html0m
142
- will 4mstill24m install the gems that you installed last time. You don't
143
- need to worry that a new release of 1merubis 22mor 1mmail 22mchanges the gems you
143
+ After checking in the Gemfile.lock into version control and cloning it
144
+ on another machine, running bundle install(1) bundle-install.1.html
145
+ will still install the gems that you installed last time. You don't
146
+ need to worry that a new release of erubis or mail changes the gems you
144
147
  use.
145
148
 
146
- However, from time to time, you might want to update the gems you are
147
- using to the newest versions that still match the gems in your Gem-
149
+ However, from time to time, you might want to update the gems you are
150
+ using to the newest versions that still match the gems in your Gem-
148
151
  file(5).
149
152
 
150
- To do this, run 1mbundle update22m, which will ignore the 1mGemfile.lock22m, and
151
- resolve all the dependencies again. Keep in mind that this process can
152
- result in a significantly different set of the 25 gems, based on the
153
- requirements of new gems that the gem authors released since the last
154
- time you ran 1mbundle update22m.
153
+ To do this, run bundle update --all, which will ignore the Gem-
154
+ file.lock, and resolve all the dependencies again. Keep in mind that
155
+ this process can result in a significantly different set of the 25
156
+ gems, based on the requirements of new gems that the gem authors
157
+ released since the last time you ran bundle update --all.
155
158
 
156
- 1mUPDATING A LIST OF GEMS0m
159
+ UPDATING A LIST OF GEMS
157
160
  Sometimes, you want to update a single gem in the Gemfile(5), and leave
158
- the rest of the gems that you specified locked to the versions in the
159
- 1mGemfile.lock22m.
161
+ the rest of the gems that you specified locked to the versions in the
162
+ Gemfile.lock.
160
163
 
161
- For instance, in the scenario above, imagine that 1mnokogiri 22mreleases
162
- version 1m1.4.422m, and you want to update it 4mwithout24m updating Rails and all
163
- of its dependencies. To do this, run 1mbundle update nokogiri22m.
164
+ For instance, in the scenario above, imagine that nokogiri releases
165
+ version 1.4.4, and you want to update it without updating Rails and all
166
+ of its dependencies. To do this, run bundle update nokogiri.
164
167
 
165
- Bundler will update 1mnokogiri 22mand any of its dependencies, but leave
168
+ Bundler will update nokogiri and any of its dependencies, but leave
166
169
  alone Rails and its dependencies.
167
170
 
168
- 1mOVERLAPPING DEPENDENCIES0m
169
- Sometimes, multiple gems declared in your Gemfile(5) are satisfied by
170
- the same second-level dependency. For instance, consider the case of
171
- 1mthin 22mand 1mrack-perftools-profiler22m.
171
+ OVERLAPPING DEPENDENCIES
172
+ Sometimes, multiple gems declared in your Gemfile(5) are satisfied by
173
+ the same second-level dependency. For instance, consider the case of
174
+ thin and rack-perftools-profiler.
172
175
 
173
176
 
174
177
 
@@ -179,8 +182,8 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
179
182
 
180
183
 
181
184
 
182
- The 1mthin 22mgem depends on 1mrack >= 1.022m, while 1mrack-perftools-profiler0m
183
- depends on 1mrack ~> 1.022m. If you run bundle install, you get:
185
+ The thin gem depends on rack >= 1.0, while rack-perftools-profiler
186
+ depends on rack ~> 1.0. If you run bundle install, you get:
184
187
 
185
188
 
186
189
 
@@ -197,86 +200,86 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
197
200
 
198
201
 
199
202
  In this case, the two gems have their own set of dependencies, but they
200
- share 1mrack 22min common. If you run 1mbundle update thin22m, bundler will
201
- update 1mdaemons22m, 1meventmachine 22mand 1mrack22m, which are dependencies of 1mthin22m,
202
- but not 1mopen4 22mor 1mperftools.rb22m, which are dependencies of
203
- 1mrack-perftools_profiler22m. Note that 1mbundle update thin 22mwill update 1mrack0m
204
- even though it's 4malso24m a dependency of 1mrack-perftools_profiler22m.
205
-
206
- In short, by default, when you update a gem using 1mbundle update22m,
207
- bundler will update all dependencies of that gem, including those that
203
+ share rack in common. If you run bundle update thin, bundler will
204
+ update daemons, eventmachine and rack, which are dependencies of thin,
205
+ but not open4 or perftools.rb, which are dependencies of
206
+ rack-perftools_profiler. Note that bundle update thin will update rack
207
+ even though it's also a dependency of rack-perftools_profiler.
208
+
209
+ In short, by default, when you update a gem using bundle update,
210
+ bundler will update all dependencies of that gem, including those that
208
211
  are also dependencies of another gem.
209
212
 
210
213
  To prevent updating shared dependencies, prior to version 1.14 the only
211
- option was the 1mCONSERVATIVE UPDATING 22mbehavior in bundle install(1) 4mbun-0m
212
- 4mdle-install.1.html24m:
214
+ option was the CONSERVATIVE UPDATING behavior in bundle install(1) bun-
215
+ dle-install.1.html:
213
216
 
214
- In this scenario, updating the 1mthin 22mversion manually in the Gemfile(5),
215
- and then running bundle install(1) 4mbundle-install.1.html24m will only
216
- update 1mdaemons 22mand 1meventmachine22m, but not 1mrack22m. For more information,
217
- see the 1mCONSERVATIVE UPDATING 22msection of bundle install(1) 4mbun-0m
218
- 4mdle-install.1.html24m.
217
+ In this scenario, updating the thin version manually in the Gemfile(5),
218
+ and then running bundle install(1) bundle-install.1.html will only
219
+ update daemons and eventmachine, but not rack. For more information,
220
+ see the CONSERVATIVE UPDATING section of bundle install(1) bun-
221
+ dle-install.1.html.
219
222
 
220
- Starting with 1.14, specifying the 1m--conservative 22moption will also pre-
223
+ Starting with 1.14, specifying the --conservative option will also pre-
221
224
  vent shared dependencies from being updated.
222
225
 
223
- 1mPATCH LEVEL OPTIONS0m
224
- Version 1.14 introduced 4 patch-level options that will influence how
225
- gem versions are resolved. One of the following options can be used:
226
- 1m--patch22m, 1m--minor 22mor 1m--major22m. 1m--strict 22mcan be added to further influence
226
+ PATCH LEVEL OPTIONS
227
+ Version 1.14 introduced 4 patch-level options that will influence how
228
+ gem versions are resolved. One of the following options can be used:
229
+ --patch, --minor or --major. --strict can be added to further influence
227
230
  resolution.
228
231
 
229
- 1m--patch0m
232
+ --patch
230
233
  Prefer updating only to next patch version.
231
234
 
232
- 1m--minor0m
235
+ --minor
233
236
  Prefer updating only to next minor version.
234
237
 
235
- 1m--major0m
238
+ --major
236
239
  Prefer updating to next major version (default).
237
240
 
238
- 1m--strict0m
239
- Do not allow any gem to be updated past latest 1m--patch 22m| 1m--minor0m
240
- | 1m--major22m.
241
+ --strict
242
+ Do not allow any gem to be updated past latest --patch | --minor
243
+ | --major.
241
244
 
242
- When Bundler is resolving what versions to use to satisfy declared
243
- requirements in the Gemfile or in parent gems, it looks up all avail-
245
+ When Bundler is resolving what versions to use to satisfy declared
246
+ requirements in the Gemfile or in parent gems, it looks up all avail-
244
247
  able versions, filters out any versions that don't satisfy the require-
245
248
  ment, and then, by default, sorts them from newest to oldest, consider-
246
249
  ing them in that order.
247
250
 
248
- Providing one of the patch level options (e.g. 1m--patch22m) changes the
249
- sort order of the satisfying versions, causing Bundler to consider the
250
- latest 1m--patch 22mor 1m--minor 22mversion available before other versions. Note
251
+ Providing one of the patch level options (e.g. --patch) changes the
252
+ sort order of the satisfying versions, causing Bundler to consider the
253
+ latest --patch or --minor version available before other versions. Note
251
254
  that versions outside the stated patch level could still be resolved to
252
255
  if necessary to find a suitable dependency graph.
253
256
 
254
- For example, if gem 'foo' is locked at 1.0.2, with no gem requirement
255
- defined in the Gemfile, and versions 1.0.3, 1.0.4, 1.1.0, 1.1.1, 2.0.0
256
- all exist, the default order of preference by default (1m--major22m) will be
257
+ For example, if gem 'foo' is locked at 1.0.2, with no gem requirement
258
+ defined in the Gemfile, and versions 1.0.3, 1.0.4, 1.1.0, 1.1.1, 2.0.0
259
+ all exist, the default order of preference by default (--major) will be
257
260
  "2.0.0, 1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2".
258
261
 
259
- If the 1m--patch 22moption is used, the order of preference will change to
262
+ If the --patch option is used, the order of preference will change to
260
263
  "1.0.4, 1.0.3, 1.0.2, 1.1.1, 1.1.0, 2.0.0".
261
264
 
262
- If the 1m--minor 22moption is used, the order of preference will change to
265
+ If the --minor option is used, the order of preference will change to
263
266
  "1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 2.0.0".
264
267
 
265
- Combining the 1m--strict 22moption with any of the patch level options will
266
- remove any versions beyond the scope of the patch level option, to
268
+ Combining the --strict option with any of the patch level options will
269
+ remove any versions beyond the scope of the patch level option, to
267
270
  ensure that no gem is updated that far.
268
271
 
269
- To continue the previous example, if both 1m--patch 22mand 1m--strict 22moptions
272
+ To continue the previous example, if both --patch and --strict options
270
273
  are used, the available versions for resolution would be "1.0.4, 1.0.3,
271
- 1.0.2". If 1m--minor 22mand 1m--strict 22mare used, it would be "1.1.1, 1.1.0,
274
+ 1.0.2". If --minor and --strict are used, it would be "1.1.1, 1.1.0,
272
275
  1.0.4, 1.0.3, 1.0.2".
273
276
 
274
- Gem requirements as defined in the Gemfile will still be the first
277
+ Gem requirements as defined in the Gemfile will still be the first
275
278
  determining factor for what versions are available. If the gem require-
276
- ment for 1mfoo 22min the Gemfile is '~> 1.0', that will accomplish the same
277
- thing as providing the 1m--minor 22mand 1m--strict 22moptions.
279
+ ment for foo in the Gemfile is '~> 1.0', that will accomplish the same
280
+ thing as providing the --minor and --strict options.
278
281
 
279
- 1mPATCH LEVEL EXAMPLES0m
282
+ PATCH LEVEL EXAMPLES
280
283
  Given the following gem specifications:
281
284
 
282
285
 
@@ -322,11 +325,11 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
322
325
 
323
326
 
324
327
 
325
- In case 1, bar is upgraded to 2.1.1, a minor version increase, because
328
+ In case 1, bar is upgraded to 2.1.1, a minor version increase, because
326
329
  the dependency from foo 1.4.5 required it.
327
330
 
328
- In case 2, only foo is requested to be unlocked, but bar is also
329
- allowed to move because it's not a declared dependency in the Gemfile.
331
+ In case 2, only foo is requested to be unlocked, but bar is also
332
+ allowed to move because it's not a declared dependency in the Gemfile.
330
333
 
331
334
  In case 3, bar goes up a whole major release, because a minor increase
332
335
  is preferred now for foo, and when it goes to 1.5.1, it requires 3.0.0
@@ -340,7 +343,7 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
340
343
  from consideration because of the --strict flag, so the most they can
341
344
  move is up to 1.4.4 and 2.0.4.
342
345
 
343
- 1mRECOMMENDED WORKFLOW0m
346
+ RECOMMENDED WORKFLOW
344
347
  In general, when working with an application managed with bundler, you
345
348
  should use the following workflow:
346
349
 
@@ -348,7 +351,7 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
348
351
 
349
352
  $ bundle install
350
353
 
351
- o Check the resulting 1mGemfile.lock 22minto version control
354
+ o Check the resulting Gemfile.lock into version control
352
355
 
353
356
  $ git add Gemfile.lock
354
357
 
@@ -366,11 +369,11 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
366
369
 
367
370
  $ bundle install
368
371
 
369
- o Make sure to check the updated 1mGemfile.lock 22minto version control
372
+ o Make sure to check the updated Gemfile.lock into version control
370
373
 
371
374
  $ git add Gemfile.lock
372
375
 
373
- o If bundle install(1) 4mbundle-install.1.html24m reports a conflict, man-
376
+ o If bundle install(1) bundle-install.1.html reports a conflict, man-
374
377
  ually update the specific gems that you changed in the Gemfile(5)
375
378
 
376
379
  $ bundle update rails thin
@@ -378,11 +381,11 @@ BUNDLE-UPDATE(1) BUNDLE-UPDATE(1)
378
381
  o If you want to update all the gems to the latest possible versions
379
382
  that still match the gems listed in the Gemfile(5), run
380
383
 
381
- $ bundle update
384
+ $ bundle update --all
382
385
 
383
386
 
384
387
 
385
388
 
386
389
 
387
390
 
388
- June 2017 BUNDLE-UPDATE(1)
391
+ December 2018 BUNDLE-UPDATE(1)