bundler 1.16.6 → 1.17.0.pre.1

data/man/bundle-package.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PACKAGE" "1" "October 2018" "" ""
+.TH "BUNDLE\-PACKAGE" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application

data/man/bundle-package.1.txt

@@ -76,4 +76,4 @@ REMOTE FETCHING
 
 
 
-				 October 2018		     BUNDLE-PACKAGE(1)
+				September 2018		     BUNDLE-PACKAGE(1)

data/man/bundle-platform.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PLATFORM" "1" "October 2018" "" ""
+.TH "BUNDLE\-PLATFORM" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-platform\fR \- Displays platform compatibility information

data/man/bundle-platform.1.txt

@@ -54,4 +54,4 @@ OPTIONS
 
 
 
-				 October 2018		    BUNDLE-PLATFORM(1)
+				September 2018		    BUNDLE-PLATFORM(1)

data/man/bundle-pristine.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PRISTINE" "1" "October 2018" "" ""
+.TH "BUNDLE\-PRISTINE" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-pristine\fR \- Restores installed gems to their pristine condition

data/man/bundle-pristine.1.txt

@@ -41,4 +41,4 @@ DESCRIPTION
 
 
 
-				 October 2018		    BUNDLE-PRISTINE(1)
+				September 2018		    BUNDLE-PRISTINE(1)

data/man/bundle-show.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-SHOW" "1" "October 2018" "" ""
+.TH "BUNDLE\-SHOW" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-show\fR \- Shows all the gems in your bundle, or the path to a gem

data/man/bundle-show.1.txt

@@ -24,4 +24,4 @@ OPTIONS
 
 
 
-				 October 2018			BUNDLE-SHOW(1)
+				September 2018			BUNDLE-SHOW(1)

data/man/bundle-update.1

@@ -1,16 +1,16 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-UPDATE" "1" "October 2018" "" ""
+.TH "BUNDLE\-UPDATE" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-update\fR \- Update your gems to the latest available versions
 .
 .SH "SYNOPSIS"
-\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]
+\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]
 .
 .SH "DESCRIPTION"
-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\.
+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\.
 .
 .P
 You would use \fBbundle update\fR to explicitly update the version of a gem\.
@@ -18,10 +18,6 @@ You would use \fBbundle update\fR to explicitly update the version of a gem\.
 .SH "OPTIONS"
 .
 .TP
-\fB\-\-all\fR
-Update all gems specified in Gemfile\.
-.
-.TP
 \fB\-\-group=<name>\fR, \fB\-g=[<name>]\fR
 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\.
 .
@@ -82,7 +78,7 @@ Do not allow any gem to be updated past latest \fB\-\-patch\fR | \fB\-\-minor\fR
 Use bundle install conservative update behavior and do not allow shared dependencies to be updated\.
 .
 .SH "UPDATING ALL GEMS"
-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\.
+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\.
 .
 .P
 Consider the following Gemfile(5):
@@ -153,7 +149,7 @@ After checking in the \fBGemfile\.lock\fR into version control and cloning it on
 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)\.
 .
 .P
-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\.
+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\.
 .
 .SH "UPDATING A LIST OF GEMS"
 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\.
@@ -388,7 +384,7 @@ $ bundle update rails thin
 If you want to update all the gems to the latest possible versions that still match the gems listed in the Gemfile(5), run
 .
 .IP
-$ bundle update \-\-all
+$ bundle update
 .
 .IP "" 0
 

data/man/bundle-update.1.txt

@@ -6,12 +6,12 @@ NAME
        bundle-update - Update your gems to the latest available versions
 
 SYNOPSIS
-       bundle  update  *gems  [--all] [--group=NAME] [--source=NAME] [--local]
-       [--ruby] [--bundler[=VERSION]] [--full-index]  [--jobs=JOBS]  [--quiet]
-       [--force] [--patch|--minor|--major] [--strict] [--conservative]
+       bundle  update  *gems [--group=NAME] [--source=NAME] [--local] [--ruby]
+       [--bundler[=VERSION]] [--full-index] [--jobs=JOBS] [--quiet]  [--force]
+       [--patch|--minor|--major] [--strict] [--conservative]
 
 DESCRIPTION
-       Update  the  gems specified (all gems, if --all flag is used), ignoring
+       Update  the  gems specified (all gems, if none are specified), ignoring
        the previously installed gems specified in the  Gemfile.lock.  In  gen-
        eral, you should use bundle install(1) bundle-install.1.html to install
        the same exact gems and versions across machines.
@@ -19,8 +19,6 @@ DESCRIPTION
        You would use bundle update to explicitly update the version of a  gem.
 
 OPTIONS
-       --all  Update all gems specified in Gemfile.
-
        --group=<name>, -g=[<name>]
 	      Only  update  the gems in the specified group. For instance, you
 	      can update all gems in the development group with bundle	update
@@ -78,9 +76,9 @@ OPTIONS
 	      shared dependencies to be updated.
 
 UPDATING ALL GEMS
-       If you run bundle update --all,	bundler  will  ignore  any  previously
-       installed  gems	and resolve all dependencies again based on the latest
-       versions of all gems available in the sources.
+       If you run bundle update 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.
 
        Consider the following Gemfile(5):
 
@@ -149,11 +147,11 @@ UPDATING ALL GEMS
        using  to  the  newest  versions that still match the gems in your Gem-
        file(5).
 
-       To do this, run	bundle	update	--all,	which  will  ignore  the  Gem-
-       file.lock,  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 bundle update --all.
+       To do this, run bundle update, which will ignore the Gemfile.lock,  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 bundle update.
 
 UPDATING A LIST OF GEMS
        Sometimes, you want to update a single gem in the Gemfile(5), and leave
@@ -380,11 +378,11 @@ RECOMMENDED WORKFLOW
        o   If you want to update all the gems to the latest possible  versions
 	   that still match the gems listed in the Gemfile(5), run
 
-	   $ bundle update --all
+	   $ bundle update
 
 
 
 
 
 
-				 October 2018		      BUNDLE-UPDATE(1)
+				September 2018		      BUNDLE-UPDATE(1)

data/man/bundle-update.ronn

@@ -3,8 +3,7 @@ bundle-update(1) -- Update your gems to the latest available versions
 
 ## SYNOPSIS
 
-`bundle update` <*gems> [--all]
-                        [--group=NAME]
+`bundle update` <*gems> [--group=NAME]
                         [--source=NAME]
                         [--local]
                         [--ruby]
@@ -19,7 +18,7 @@ bundle-update(1) -- Update your gems to the latest available versions
 
 ## DESCRIPTION
 
-Update the gems specified (all gems, if `--all` flag is used), ignoring
+Update the gems specified (all gems, if none are specified), ignoring
 the previously installed gems specified in the `Gemfile.lock`. In
 general, you should use [bundle install(1)](bundle-install.1.html) to install the same exact
 gems and versions across machines.
@@ -29,9 +28,6 @@ gem.
 
 ## OPTIONS
 
-* `--all`:
-  Update all gems specified in Gemfile.
-
 * `--group=<name>`, `-g=[<name>]`:
   Only update the gems in the specified group. For instance, you can update all gems
   in the development group with `bundle update --group development`. You can also
@@ -84,7 +80,7 @@ gem.
 
 ## UPDATING ALL GEMS
 
-If you run `bundle update --all`, bundler will ignore
+If you run `bundle update` 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.
 
@@ -143,10 +139,10 @@ the gems you use.
 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).
 
-To do this, run `bundle update --all`, which will ignore the `Gemfile.lock`, and resolve
+To do this, run `bundle update`, which will ignore the `Gemfile.lock`, 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 `bundle update --all`.
+authors released since the last time you ran `bundle update`.
 
 ## UPDATING A LIST OF GEMS
 
@@ -347,4 +343,4 @@ use the following workflow:
 * If you want to update all the gems to the latest possible versions that
   still match the gems listed in the Gemfile(5), run
 
-    $ bundle update --all
+    $ bundle update

data/man/bundle-viz.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-VIZ" "1" "October 2018" "" ""
+.TH "BUNDLE\-VIZ" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-viz\fR \- Generates a visual dependency graph for your Gemfile

data/man/bundle-viz.1.txt

@@ -36,4 +36,4 @@ OPTIONS
 
 
 
-				 October 2018			 BUNDLE-VIZ(1)
+				September 2018			 BUNDLE-VIZ(1)

data/man/bundle.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE" "1" "October 2018" "" ""
+.TH "BUNDLE" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\fR \- Ruby Dependency Management

data/man/bundle.1.txt

@@ -110,4 +110,4 @@ OBSOLETE
 
 
 
-				 October 2018			     BUNDLE(1)
+				September 2018			     BUNDLE(1)

data/man/gemfile.5

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "GEMFILE" "5" "October 2018" "" ""
+.TH "GEMFILE" "5" "September 2018" "" ""
 .
 .SH "NAME"
 \fBGemfile\fR \- A format for describing gem dependencies for Ruby programs

data/man/gemfile.5.txt

@@ -650,4 +650,4 @@ SOURCE PRIORITY
 
 
 
-				 October 2018			    GEMFILE(5)
+				September 2018			    GEMFILE(5)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: bundler
 version: !ruby/object:Gem::Version
-  version: 1.16.6
+  version: 1.17.0.pre.1
 platform: ruby
 authors:
 - André Arko
@@ -10,7 +10,6 @@ authors:
 - Hiroshi Shibata
 - David Rodríguez
 - Grey Baker
-- Stephanie Morillo
 - Chris Morris
 - James Wen
 - Tim Moore
@@ -22,7 +21,7 @@ authors:
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2018-10-05 00:00:00.000000000 Z
+date: 2018-09-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: automatiek
@@ -203,6 +202,7 @@ files:
 - lib/bundler/plugin/api.rb
 - lib/bundler/plugin/api/source.rb
 - lib/bundler/plugin/dsl.rb
+- lib/bundler/plugin/events.rb
 - lib/bundler/plugin/index.rb
 - lib/bundler/plugin/installer.rb
 - lib/bundler/plugin/installer/git.rb