v1.1.pre.3

Features:

• Add bundle outdated to show outdated gems (@joelmoss)
• Remove BUNDLE_* from Bundler.with_clean_env (@wuputah)
• Add Bundler.clean_system, and clean_exec (@wuputah)
• Use git config for gem author name and email (@krekoten)

Bugfixes:

• Fix error calling Bundler.rubygems.gem_path
• Fix error when Gem.path returns Gem::FS instead of String

1.1.pre.2 (April 28, 2011)

Features:

• Add :github option to Gemfile DSL for easy git repos
• Merge all fixes from 1.0.12 and 1.0.13

1.1.pre.1 (February 2, 2011)

Bugfixes:

• Compatibility with changes made by Rubygems 1.5

1.1.pre (January 21, 2011)

Features:

• Add bundle clean. Removes unused gems from --path directory
• Initial Gemcutter Endpoint API work, BAI Fetching source index
• Added bundle install --standalone
• Ignore Gemfile.lock when building new gems
• Make it possible to override a .gemspec dependency's source in the
  Gemfile

Removed:

• Removed bundle lock
• Removed bundle install
• Removed bundle install --production
• Removed bundle install --disable-shared-gems

v1.0.13

Features:

• Compatibility with Rubygems master (soon to be v1.8) (@evanphx)
• Informative error when --path points to a broken symlink
• Support Rake 0.9 and greater (@e2)
• Output full errors for non-TTYs e.g. pow (@josh)

Bugfixes:

• Allow spaces in gem path names for gem tasks (@rslifka)
• Have cap run bundle install from release_path (@martinjagusch)
• Quote git refspec so zsh doesn't expand it (@goneflyin)

1.0.12 (April 8, 2011)

Features:

• Add --no-deployment option to install for disabling it on dev machines
• Better error message when git fails and cache is present (@parndt)
• Honor :bundle_cmd in cap rake command (@voidlock, @cgriego)

Bugfixes:

• Compatibility with Rubygems 1.7 and Rails 2.3 and vendored gems (@evanphx)
• Fix changing gem order in lock (@gucki)
• Remove color escape sequences when displaying man pages (@bgreenlee)
• Fix creating GEM_HOME on both JRuby 1.5 and 1.6 (@nickseiger)
• Fix gems without a gemspec and directories in bin/ (@epall)
• Fix --no-prune option for bundle install (@cmeiklejohn)

1.0.11 (April 1, 2011)

Features:

• Compatibility with Rubygems 1.6 and 1.7
• Better error messages when a git command fails

Bugfixes:

• Don't always update gemspec gems (@carllerche)
• Remove ivar warnings (@jackdempsey)
• Fix occasional git failures in zsh (@jonah-carbonfive)
• Consistent lock for gems with double deps like Cap (@akahn)

1.0.10 (February 1, 2011)

Bugfixes:

• Fix a regression loading YAML gemspecs from :git and :path gems
• Requires, namespaces, etc. to work with changes in Rubygems 1.5

1.0.9 (January 19, 2011)

Bugfixes:

• Fix a bug where Bundler.require could remove gems from the load
  path. In Rails apps with a default application.rb, this removed
  all gems in groups other than :default and Rails.env

1.0.8 (January 18, 2011)

Features:

• Allow overriding gemspec() deps with :git deps
• Add --local option to bundle update
• Ignore Gemfile.lock in newly generated gems
• Use less as help pager instead of more
• Run bundle exec rake instead of rake in Capistrano tasks

Bugfixes:

• Fix --no-cache option for bundle install
• Allow Vlad deploys to work without Capistrano gem installed
• Fix group arguments to bundle console
• Allow groups to be loaded even if other groups were loaded
• Evaluate gemspec() gemspecs in their directory not the cwd
• Count on Rake to chdir to the right place in GemHelper
• Change Pathnames to Strings for MacRuby
• Check git process exit status correctly
• Fix some warnings in 1.9.3-trunk (thanks tenderlove)

1.0.7 (November 17, 2010)

Bugfixes:

• Remove Bundler version from the lockfile because it broke
  backwards compatibility with 1.0.0-1.0.5. Sorry. :(

1.0.6 (November 16, 2010)

Bugfixes:

• Fix regression in update that caused long/wrong results
• Allow git gems on other platforms while installing (#579)

Features:

• Speed up install command using various optimizations
• Significantly increase performance of resolver
• Use upcoming Rubygems performance improvements (@tmm1)
• Warn if the lockfile was generated by a newer version
• Set generated gems' homepage to "", so Rubygems will warn

1.0.5 (November 13, 2010)

Bugfixes:

• Fix regression disabling all operations that employ sudo

1.0.4 (November 12, 2010)

Bugfixes:

• Expand relative :paths from Bundler.root (eg ./foogem)
• Allow git gems in --without groups while --frozen
• Allow gem :ref to be a symbol as well as a string
• Fix exception when Gemfile needs a newer Bundler version
• Explanation when the current Bundler version conflicts
• Explicit error message if Gemfile needs newer Bundler
• Ignore an empty string BUNDLE_GEMFILE
• Skeleton gemspec now works with older versions of git
• Fix shell quoting and ref fetching in GemHelper
• Disable colored output in --deployment
• Preserve line endings in lock file

Features:

• Add support for 'mingw32' platform (aka RubyInstaller)
• Large speed increase when Gemfile.lock is already present
• Huge speed increase when many (100+) system gems are present
• Significant expansion of ISSUES, man pages, and docs site
• Remove Open3 from GemHelper (now it works on Windows™®©)
• Allow setting roles in built-in cap and vlad tasks

1.0.3 (October 15, 2010)

Bugfixes:

• Use bitwise or in #hash to reduce the chance of overflow
• bundle update now works with :git + :tag updates
• Record relative :path options in the Gemfile.lock
• :groups option on gem method in Gemfile now works
• Add #platform method and :platform option to Gemfile DSL
• --without now accepts a quoted, space-separated list
• Installing after --deployment with no lock is now possible
• Binstubs can now be symlinked
• Print warning if cache for --local install is missing gems
• Improve output when installing to a path
• The tests all pass! Yay!

1.0.2 (October 2, 2010)

Bugfix:

• Actually include the man pages in the gem, so help works

1.0.1 (October 1, 2010)

Features:

• Vlad deployment recipe, require 'bundler/vlad'
• Prettier bundle graphs
• Improved gem skeleton for bundle gem
• Prompt on file clashes when generating a gem
• Option to generate binary with gem skeleton
• Allow subclassing of GemHelper for custom tasks
• Chdir to gem directory during bundle open

Bugfixes:

• Allow gemspec requirements with a list of versions
• Accept lockfiles with windows line endings
• Respect BUNDLE_WITHOUT env var
• Allow gem "foo", :platform => :jruby
• Specify loaded_from path in fake gemspec
• Flesh out gem_helper tasks, raise errors correctly
• Respect RBConfig::CONFIG['ruby_install_name'] in binstubs

1.0.0 (August 29, 2010)

Features:

• You can now define :bundle_cmd in the capistrano task

Bugfixes:

• Various bugfixes to the built-in rake helpers
• Fix a bug where shortrefs weren't unique enough and were
  therfore colliding
• Fix a small bug involving checking whether a local git
  clone is up to date
• Correctly handle explicit '=' dependencies with gems
  pinned to a git source
• Fix an issue with Windows-generated lockfiles by reading
  and writing the lockfile in binary mode
• Fix an issue with shelling out to git in Windows by
  using double quotes around paths
• Detect new Rubygems sources in the Gemfile and update
  the lockfile

1.0.0.rc.6 (August 23, 2010)

Features:

• Much better documentation for most of the commands and Gemfile
  format

Bugfixes:

• Don't attempt to create directories if they already exist
• Fix the capistrano task so that it actually runs
• Update the Gemfile template to reference rubygems.org instead
  of :gemcutter
• bundle exec should exit with a non zero exit code when the gem
  binary does not exist or the file is not executable.
• Expand paths in Gemfile relative to the Gemfile and not the current
  working directory.

1.0.0.rc.5 (August 10, 2010)

Features:

• Make the Capistrano task more concise.

Bugfixes:

• Fix a regression with determining whether or not to use sudo
• Allow using the --gemfile flag with the --deployment flag

1.0.0.rc.4 (August 9, 2010)

Features:

• bundle gem NAME command to generate a new gem with Gemfile
• Bundle config file location can be specified by BUNDLE_APP_CONFIG
• Add --frozen to disable updating the Gemfile.lock at runtime
  (default with --deployment)
• Basic Capistrano task now added as 'bundler/capistrano'

Bugfixes:

• Multiple bundler process no longer share a tmp directory
• bundle update GEM always updates dependencies of GEM as well
• Deleting the cache directory no longer causes errors
• Moving the bundle after installation no longer causes git errors
• Bundle path is now correctly remembered on a read-only filesystem
• Gem binaries are installed to Gem.bindir, not #{Gem.dir}/bin
• Fetch gems from vendor/cache, even without --local
• Sort lockfile by platform as well as spec

1.0.0.rc.3 (August 3, 2010)

Features:

• Deprecate --production flag for --deployment, since the former
  was causing confusion with the :production group
• Add --gemfile option to bundle check
• Reduce memory usage of bundle install by 2-4x
• Improve message from bundle check under various conditions
• Better error when a changed Gemfile conflicts with Gemfile.lock

Bugfixes:

• Create bin/ directory if it is missing, then install binstubs
• Error nicely on the edge case of a pinned gem with no spec
• Do not require gems for other platforms
• Update git sources along with the gems they contain

1.0.0.rc.2 (July 29, 2010)

• bundle install path was causing confusion, so we now print
  a clarifying warning. The preferred way to install to a path
  (which will not print the warning) is
  bundle install --path path/to/install.
• bundle install --system installs to the default system
  location ($BUNDLE_PATH or $GEM_HOME) even if you previously
  used bundle install --path
• completely remove --disable-shared-gems. If you install to
  system, you will not be isolated, while if you install to
  another path, you will be isolated from gems installed to
  the system. This was mostly an internal option whose naming
  and semantics were extremely confusing.
• Add a --production option to bundle install:
  • by default, installs to vendor/bundle. This can be
    overridden with the --path option
  • uses --local if vendor/cache is found. This will
    guarantee that Bundler does not attempt to connect to
    Rubygems and will use the gems cached in vendor/cache
    instead
  • Raises an exception if a Gemfile.lock is not found
  • Raises an exception if you modify your Gemfile in development
    but do not check in an updated Gemfile.lock
• Fixes a bug where switch...

v1.1.pre.2

Features:

• Add :github option to Gemfile DSL for easy git repos
• Merge all fixes from 1.0.12 and 1.0.13

1.1.pre.1 (February 2, 2011)

Bugfixes:

• Compatibility with changes made by Rubygems 1.5

1.1.pre (January 21, 2011)

Features:

• Add bundle clean. Removes unused gems from --path directory
• Initial Gemcutter Endpoint API work, BAI Fetching source index
• Added bundle install --standalone
• Ignore Gemfile.lock when building new gems
• Make it possible to override a .gemspec dependency's source in the
  Gemfile

Removed:

• Removed bundle lock
• Removed bundle install
• Removed bundle install --production
• Removed bundle install --disable-shared-gems

v1.0.12

Features:

• Add --no-deployment option to install for disabling it on dev machines
• Better error message when git fails and cache is present (@parndt)
• Honor :bundle_cmd in cap rake command (@voidlock, @cgriego)

Bugfixes:

• Compatibility with Rubygems 1.7 and Rails 2.3 and vendored gems (@evanphx)
• Fix changing gem order in lock (@gucki)
• Remove color escape sequences when displaying man pages (@bgreenlee)
• Fix creating GEM_HOME on both JRuby 1.5 and 1.6 (@nickseiger)
• Fix gems without a gemspec and directories in bin/ (@epall)
• Fix --no-prune option for bundle install (@cmeiklejohn)

1.0.11 (April 1, 2011)

Features:

• Compatibility with Rubygems 1.6 and 1.7
• Better error messages when a git command fails

Bugfixes:

• Don't always update gemspec gems (@carllerche)
• Remove ivar warnings (@jackdempsey)
• Fix occasional git failures in zsh (@jonah-carbonfive)
• Consistent lock for gems with double deps like Cap (@akahn)

1.0.10 (February 1, 2011)

Bugfixes:

• Fix a regression loading YAML gemspecs from :git and :path gems
• Requires, namespaces, etc. to work with changes in Rubygems 1.5

1.0.9 (January 19, 2011)

Bugfixes:

• Fix a bug where Bundler.require could remove gems from the load
  path. In Rails apps with a default application.rb, this removed
  all gems in groups other than :default and Rails.env

1.0.8 (January 18, 2011)

Features:

• Allow overriding gemspec() deps with :git deps
• Add --local option to bundle update
• Ignore Gemfile.lock in newly generated gems
• Use less as help pager instead of more
• Run bundle exec rake instead of rake in Capistrano tasks

Bugfixes:

• Fix --no-cache option for bundle install
• Allow Vlad deploys to work without Capistrano gem installed
• Fix group arguments to bundle console
• Allow groups to be loaded even if other groups were loaded
• Evaluate gemspec() gemspecs in their directory not the cwd
• Count on Rake to chdir to the right place in GemHelper
• Change Pathnames to Strings for MacRuby
• Check git process exit status correctly
• Fix some warnings in 1.9.3-trunk (thanks tenderlove)

1.0.7 (November 17, 2010)

Bugfixes:

• Remove Bundler version from the lockfile because it broke
  backwards compatibility with 1.0.0-1.0.5. Sorry. :(

1.0.6 (November 16, 2010)

Bugfixes:

• Fix regression in update that caused long/wrong results
• Allow git gems on other platforms while installing (#579)

Features:

• Speed up install command using various optimizations
• Significantly increase performance of resolver
• Use upcoming Rubygems performance improvements (@tmm1)
• Warn if the lockfile was generated by a newer version
• Set generated gems' homepage to "", so Rubygems will warn

1.0.5 (November 13, 2010)

Bugfixes:

• Fix regression disabling all operations that employ sudo

1.0.4 (November 12, 2010)

Bugfixes:

• Expand relative :paths from Bundler.root (eg ./foogem)
• Allow git gems in --without groups while --frozen
• Allow gem :ref to be a symbol as well as a string
• Fix exception when Gemfile needs a newer Bundler version
• Explanation when the current Bundler version conflicts
• Explicit error message if Gemfile needs newer Bundler
• Ignore an empty string BUNDLE_GEMFILE
• Skeleton gemspec now works with older versions of git
• Fix shell quoting and ref fetching in GemHelper
• Disable colored output in --deployment
• Preserve line endings in lock file

Features:

• Add support for 'mingw32' platform (aka RubyInstaller)
• Large speed increase when Gemfile.lock is already present
• Huge speed increase when many (100+) system gems are present
• Significant expansion of ISSUES, man pages, and docs site
• Remove Open3 from GemHelper (now it works on Windows™®©)
• Allow setting roles in built-in cap and vlad tasks

1.0.3 (October 15, 2010)

Bugfixes:

• Use bitwise or in #hash to reduce the chance of overflow
• bundle update now works with :git + :tag updates
• Record relative :path options in the Gemfile.lock
• :groups option on gem method in Gemfile now works
• Add #platform method and :platform option to Gemfile DSL
• --without now accepts a quoted, space-separated list
• Installing after --deployment with no lock is now possible
• Binstubs can now be symlinked
• Print warning if cache for --local install is missing gems
• Improve output when installing to a path
• The tests all pass! Yay!

1.0.2 (October 2, 2010)

Bugfix:

• Actually include the man pages in the gem, so help works

1.0.1 (October 1, 2010)

Features:

• Vlad deployment recipe, require 'bundler/vlad'
• Prettier bundle graphs
• Improved gem skeleton for bundle gem
• Prompt on file clashes when generating a gem
• Option to generate binary with gem skeleton
• Allow subclassing of GemHelper for custom tasks
• Chdir to gem directory during bundle open

Bugfixes:

• Allow gemspec requirements with a list of versions
• Accept lockfiles with windows line endings
• Respect BUNDLE_WITHOUT env var
• Allow gem "foo", :platform => :jruby
• Specify loaded_from path in fake gemspec
• Flesh out gem_helper tasks, raise errors correctly
• Respect RBConfig::CONFIG['ruby_install_name'] in binstubs

1.0.0 (August 29, 2010)

Features:

• You can now define :bundle_cmd in the capistrano task

Bugfixes:

• Various bugfixes to the built-in rake helpers
• Fix a bug where shortrefs weren't unique enough and were
  therfore colliding
• Fix a small bug involving checking whether a local git
  clone is up to date
• Correctly handle explicit '=' dependencies with gems
  pinned to a git source
• Fix an issue with Windows-generated lockfiles by reading
  and writing the lockfile in binary mode
• Fix an issue with shelling out to git in Windows by
  using double quotes around paths
• Detect new Rubygems sources in the Gemfile and update
  the lockfile

1.0.0.rc.6 (August 23, 2010)

Features:

• Much better documentation for most of the commands and Gemfile
  format

Bugfixes:

• Don't attempt to create directories if they already exist
• Fix the capistrano task so that it actually runs
• Update the Gemfile template to reference rubygems.org instead
  of :gemcutter
• bundle exec should exit with a non zero exit code when the gem
  binary does not exist or the file is not executable.
• Expand paths in Gemfile relative to the Gemfile and not the current
  working directory.

1.0.0.rc.5 (August 10, 2010)

Features:

• Make the Capistrano task more concise.

Bugfixes:

• Fix a regression with determining whether or not to use sudo
• Allow using the --gemfile flag with the --deployment flag

1.0.0.rc.4 (August 9, 2010)

Features:

• bundle gem NAME command to generate a new gem with Gemfile
• Bundle config file location can be specified by BUNDLE_APP_CONFIG
• Add --frozen to disable updating the Gemfile.lock at runtime
  (default with --deployment)
• Basic Capistrano task now added as 'bundler/capistrano'

Bugfixes:

• Multiple bundler process no longer share a tmp directory
• bundle update GEM always updates dependencies of GEM as well
• Deleting the cache directory no longer causes errors
• Moving the bundle after installation no longer causes git errors
• Bundle path is now correctly remembered on a read-only filesystem
• Gem binaries are installed to Gem.bindir, not #{Gem.dir}/bin
• Fetch gems from vendor/cache, even without --local
• Sort lockfile by platform as well as spec

1.0.0.rc.3 (August 3, 2010)

Features:

• Deprecate --production flag for --deployment, since the former
  was causing confusion with the :production group
• Add --gemfile option to bundle check
• Reduce memory usage of bundle install by 2-4x
• Improve message from bundle check under various conditions
• Better error when a changed Gemfile conflicts with Gemfile.lock

Bugfixes:

• Create bin/ directory if it is missing, then install binstubs
• Error nicely on the edge case of a pinned gem with no spec
• Do not require gems for other platforms
• Update git sources along with the gems they contain

1.0.0.rc.2 (July 29, 2010)

• bundle install path was causing confusion, so we now print
  a clarifying warning. The preferred way to install to a path
  (which will not print the warning) is
  bundle install --path path/to/install.
• bundle install --system installs to the default system
  location ($BUNDLE_PATH or $GEM_HOME) even if you previously
  used bundle install --path
• completely remove --disable-shared-gems. If you install to
  system, you will not be isolated, while if you install to
  another path, you will be isolated from gems installed to
  the system. This was mostly an internal option whose naming
  and semantics were extremely confusing.
• Add a --production option to bundle install:
  • by default, installs to vendor/bundle. This can be
    overridden with the --path option
  • uses --local if vendor/cache is found. This will
    guarantee that Bundler does not attempt to connect to
    Rubygems and will use the gems cached in vendor/cache
    instead
  • Raises an exception if a Gemfile.lock is not found
  • Raises an exception if you modify your Gemfile in development
    but do not check in an updated Gemfile.lock
• Fixes a bug where switching a source from Rubygems to git
  would always say "the git source is not checked out" when
  running bundle install

NOTE: We received several reports of "the git source has not
been checked out. Please run bundle install". As far as we
can tell, these problems have two possible causes:

1. bundle install ~/.bundle in one user, but actually running
   the application as another user. Never install gems to a
   directory scoped to a user (~ or...

v1.0.11

Features:

• Compatibility with Rubygems 1.6 and 1.7
• Better error messages when a git command fails

Bugfixes:

• Don't always update gemspec gems (@carllerche)
• Remove ivar warnings (@jackdempsey)
• Fix occasional git failures in zsh (@jonah-carbonfive)
• Consistent lock for gems with double deps like Cap (@akahn)

1.0.10 (February 1, 2011)

Bugfixes:

• Fix a regression loading YAML gemspecs from :git and :path gems
• Requires, namespaces, etc. to work with changes in Rubygems 1.5

1.0.9 (January 19, 2011)

Bugfixes:

• Fix a bug where Bundler.require could remove gems from the load
  path. In Rails apps with a default application.rb, this removed
  all gems in groups other than :default and Rails.env

1.0.8 (January 18, 2011)

Features:

• Allow overriding gemspec() deps with :git deps
• Add --local option to bundle update
• Ignore Gemfile.lock in newly generated gems
• Use less as help pager instead of more
• Run bundle exec rake instead of rake in Capistrano tasks

Bugfixes:

• Fix --no-cache option for bundle install
• Allow Vlad deploys to work without Capistrano gem installed
• Fix group arguments to bundle console
• Allow groups to be loaded even if other groups were loaded
• Evaluate gemspec() gemspecs in their directory not the cwd
• Count on Rake to chdir to the right place in GemHelper
• Change Pathnames to Strings for MacRuby
• Check git process exit status correctly
• Fix some warnings in 1.9.3-trunk (thanks tenderlove)

1.0.7 (November 17, 2010)

Bugfixes:

• Remove Bundler version from the lockfile because it broke
  backwards compatibility with 1.0.0-1.0.5. Sorry. :(

1.0.6 (November 16, 2010)

Bugfixes:

• Fix regression in update that caused long/wrong results
• Allow git gems on other platforms while installing (#579)

Features:

• Speed up install command using various optimizations
• Significantly increase performance of resolver
• Use upcoming Rubygems performance improvements (@tmm1)
• Warn if the lockfile was generated by a newer version
• Set generated gems' homepage to "", so Rubygems will warn

1.0.5 (November 13, 2010)

Bugfixes:

• Fix regression disabling all operations that employ sudo

1.0.4 (November 12, 2010)

Bugfixes:

• Expand relative :paths from Bundler.root (eg ./foogem)
• Allow git gems in --without groups while --frozen
• Allow gem :ref to be a symbol as well as a string
• Fix exception when Gemfile needs a newer Bundler version
• Explanation when the current Bundler version conflicts
• Explicit error message if Gemfile needs newer Bundler
• Ignore an empty string BUNDLE_GEMFILE
• Skeleton gemspec now works with older versions of git
• Fix shell quoting and ref fetching in GemHelper
• Disable colored output in --deployment
• Preserve line endings in lock file

Features:

• Add support for 'mingw32' platform (aka RubyInstaller)
• Large speed increase when Gemfile.lock is already present
• Huge speed increase when many (100+) system gems are present
• Significant expansion of ISSUES, man pages, and docs site
• Remove Open3 from GemHelper (now it works on Windows™®©)
• Allow setting roles in built-in cap and vlad tasks

1.0.3 (October 15, 2010)

Bugfixes:

• Use bitwise or in #hash to reduce the chance of overflow
• bundle update now works with :git + :tag updates
• Record relative :path options in the Gemfile.lock
• :groups option on gem method in Gemfile now works
• Add #platform method and :platform option to Gemfile DSL
• --without now accepts a quoted, space-separated list
• Installing after --deployment with no lock is now possible
• Binstubs can now be symlinked
• Print warning if cache for --local install is missing gems
• Improve output when installing to a path
• The tests all pass! Yay!

1.0.2 (October 2, 2010)

Bugfix:

• Actually include the man pages in the gem, so help works

1.0.1 (October 1, 2010)

Features:

• Vlad deployment recipe, require 'bundler/vlad'
• Prettier bundle graphs
• Improved gem skeleton for bundle gem
• Prompt on file clashes when generating a gem
• Option to generate binary with gem skeleton
• Allow subclassing of GemHelper for custom tasks
• Chdir to gem directory during bundle open

Bugfixes:

• Allow gemspec requirements with a list of versions
• Accept lockfiles with windows line endings
• Respect BUNDLE_WITHOUT env var
• Allow gem "foo", :platform => :jruby
• Specify loaded_from path in fake gemspec
• Flesh out gem_helper tasks, raise errors correctly
• Respect RBConfig::CONFIG['ruby_install_name'] in binstubs

1.0.0 (August 29, 2010)

Features:

• You can now define :bundle_cmd in the capistrano task

Bugfixes:

• Various bugfixes to the built-in rake helpers
• Fix a bug where shortrefs weren't unique enough and were
  therfore colliding
• Fix a small bug involving checking whether a local git
  clone is up to date
• Correctly handle explicit '=' dependencies with gems
  pinned to a git source
• Fix an issue with Windows-generated lockfiles by reading
  and writing the lockfile in binary mode
• Fix an issue with shelling out to git in Windows by
  using double quotes around paths
• Detect new Rubygems sources in the Gemfile and update
  the lockfile

1.0.0.rc.6 (August 23, 2010)

Features:

• Much better documentation for most of the commands and Gemfile
  format

Bugfixes:

• Don't attempt to create directories if they already exist
• Fix the capistrano task so that it actually runs
• Update the Gemfile template to reference rubygems.org instead
  of :gemcutter
• bundle exec should exit with a non zero exit code when the gem
  binary does not exist or the file is not executable.
• Expand paths in Gemfile relative to the Gemfile and not the current
  working directory.

1.0.0.rc.5 (August 10, 2010)

Features:

• Make the Capistrano task more concise.

Bugfixes:

• Fix a regression with determining whether or not to use sudo
• Allow using the --gemfile flag with the --deployment flag

1.0.0.rc.4 (August 9, 2010)

Features:

• bundle gem NAME command to generate a new gem with Gemfile
• Bundle config file location can be specified by BUNDLE_APP_CONFIG
• Add --frozen to disable updating the Gemfile.lock at runtime
  (default with --deployment)
• Basic Capistrano task now added as 'bundler/capistrano'

Bugfixes:

• Multiple bundler process no longer share a tmp directory
• bundle update GEM always updates dependencies of GEM as well
• Deleting the cache directory no longer causes errors
• Moving the bundle after installation no longer causes git errors
• Bundle path is now correctly remembered on a read-only filesystem
• Gem binaries are installed to Gem.bindir, not #{Gem.dir}/bin
• Fetch gems from vendor/cache, even without --local
• Sort lockfile by platform as well as spec

1.0.0.rc.3 (August 3, 2010)

Features:

• Deprecate --production flag for --deployment, since the former
  was causing confusion with the :production group
• Add --gemfile option to bundle check
• Reduce memory usage of bundle install by 2-4x
• Improve message from bundle check under various conditions
• Better error when a changed Gemfile conflicts with Gemfile.lock

Bugfixes:

• Create bin/ directory if it is missing, then install binstubs
• Error nicely on the edge case of a pinned gem with no spec
• Do not require gems for other platforms
• Update git sources along with the gems they contain

1.0.0.rc.2 (July 29, 2010)

• bundle install path was causing confusion, so we now print
  a clarifying warning. The preferred way to install to a path
  (which will not print the warning) is
  bundle install --path path/to/install.
• bundle install --system installs to the default system
  location ($BUNDLE_PATH or $GEM_HOME) even if you previously
  used bundle install --path
• completely remove --disable-shared-gems. If you install to
  system, you will not be isolated, while if you install to
  another path, you will be isolated from gems installed to
  the system. This was mostly an internal option whose naming
  and semantics were extremely confusing.
• Add a --production option to bundle install:
  • by default, installs to vendor/bundle. This can be
    overridden with the --path option
  • uses --local if vendor/cache is found. This will
    guarantee that Bundler does not attempt to connect to
    Rubygems and will use the gems cached in vendor/cache
    instead
  • Raises an exception if a Gemfile.lock is not found
  • Raises an exception if you modify your Gemfile in development
    but do not check in an updated Gemfile.lock
• Fixes a bug where switching a source from Rubygems to git
  would always say "the git source is not checked out" when
  running bundle install

NOTE: We received several reports of "the git source has not
been checked out. Please run bundle install". As far as we
can tell, these problems have two possible causes:

1. bundle install ~/.bundle in one user, but actually running
   the application as another user. Never install gems to a
   directory scoped to a user (~ or $HOME) in deployment.
2. A bug that happened when changing a gem to a git source.

To mitigate several common causes of (1), please use the
new --production flag. This flag is simply a roll-up of
the best practices we have been encouraging people to use
for deployment.

If you want to share gems across deployments, and you use
Capistrano, symlink release_path/current/vendor/bundle to
release_path/shared/bundle. This will keep deployments
snappy while maintaining the benefits of clean, deploy-time
isolation.

1.0.0.rc.1 (July 26, 2010)

• Fixed a bug with bundle install on multiple machines and git

1.0.0.beta.10 (July 25, 2010)

...

v1.1.pre.1

Bugfixes:

• Compatibility with changes made by Rubygems 1.5

1.1.pre (January 21, 2011)

Features:

• Add bundle clean. Removes unused gems from --path directory
• Initial Gemcutter Endpoint API work, BAI Fetching source index
• Added bundle install --standalone
• Ignore Gemfile.lock when building new gems
• Make it possible to override a .gemspec dependency's source in the
  Gemfile

Removed:

• Removed bundle lock
• Removed bundle install
• Removed bundle install --production
• Removed bundle install --disable-shared-gems

v1.0.10

Bugfixes:

• Fix a regression loading YAML gemspecs from :git and :path gems
• Requires, namespaces, etc. to work with changes in Rubygems 1.5

1.0.9 (January 19, 2011)

Bugfixes:

• Fix a bug where Bundler.require could remove gems from the load
  path. In Rails apps with a default application.rb, this removed
  all gems in groups other than :default and Rails.env

1.0.8 (January 18, 2011)

Features:

• Allow overriding gemspec() deps with :git deps
• Add --local option to bundle update
• Ignore Gemfile.lock in newly generated gems
• Use less as help pager instead of more
• Run bundle exec rake instead of rake in Capistrano tasks

Bugfixes:

• Fix --no-cache option for bundle install
• Allow Vlad deploys to work without Capistrano gem installed
• Fix group arguments to bundle console
• Allow groups to be loaded even if other groups were loaded
• Evaluate gemspec() gemspecs in their directory not the cwd
• Count on Rake to chdir to the right place in GemHelper
• Change Pathnames to Strings for MacRuby
• Check git process exit status correctly
• Fix some warnings in 1.9.3-trunk (thanks tenderlove)

1.0.7 (November 17, 2010)

Bugfixes:

• Remove Bundler version from the lockfile because it broke
  backwards compatibility with 1.0.0-1.0.5. Sorry. :(

1.0.6 (November 16, 2010)

Bugfixes:

• Fix regression in update that caused long/wrong results
• Allow git gems on other platforms while installing (#579)

Features:

• Speed up install command using various optimizations
• Significantly increase performance of resolver
• Use upcoming Rubygems performance improvements (@tmm1)
• Warn if the lockfile was generated by a newer version
• Set generated gems' homepage to "", so Rubygems will warn

1.0.5 (November 13, 2010)

Bugfixes:

• Fix regression disabling all operations that employ sudo

1.0.4 (November 12, 2010)

Bugfixes:

• Expand relative :paths from Bundler.root (eg ./foogem)
• Allow git gems in --without groups while --frozen
• Allow gem :ref to be a symbol as well as a string
• Fix exception when Gemfile needs a newer Bundler version
• Explanation when the current Bundler version conflicts
• Explicit error message if Gemfile needs newer Bundler
• Ignore an empty string BUNDLE_GEMFILE
• Skeleton gemspec now works with older versions of git
• Fix shell quoting and ref fetching in GemHelper
• Disable colored output in --deployment
• Preserve line endings in lock file

Features:

• Add support for 'mingw32' platform (aka RubyInstaller)
• Large speed increase when Gemfile.lock is already present
• Huge speed increase when many (100+) system gems are present
• Significant expansion of ISSUES, man pages, and docs site
• Remove Open3 from GemHelper (now it works on Windows™®©)
• Allow setting roles in built-in cap and vlad tasks

1.0.3 (October 15, 2010)

Bugfixes:

• Use bitwise or in #hash to reduce the chance of overflow
• bundle update now works with :git + :tag updates
• Record relative :path options in the Gemfile.lock
• :groups option on gem method in Gemfile now works
• Add #platform method and :platform option to Gemfile DSL
• --without now accepts a quoted, space-separated list
• Installing after --deployment with no lock is now possible
• Binstubs can now be symlinked
• Print warning if cache for --local install is missing gems
• Improve output when installing to a path
• The tests all pass! Yay!

1.0.2 (October 2, 2010)

Bugfix:

• Actually include the man pages in the gem, so help works

1.0.1 (October 1, 2010)

Features:

• Vlad deployment recipe, require 'bundler/vlad'
• Prettier bundle graphs
• Improved gem skeleton for bundle gem
• Prompt on file clashes when generating a gem
• Option to generate binary with gem skeleton
• Allow subclassing of GemHelper for custom tasks
• Chdir to gem directory during bundle open

Bugfixes:

• Allow gemspec requirements with a list of versions
• Accept lockfiles with windows line endings
• Respect BUNDLE_WITHOUT env var
• Allow gem "foo", :platform => :jruby
• Specify loaded_from path in fake gemspec
• Flesh out gem_helper tasks, raise errors correctly
• Respect RBConfig::CONFIG['ruby_install_name'] in binstubs

1.0.0 (August 29, 2010)

Features:

• You can now define :bundle_cmd in the capistrano task

Bugfixes:

• Various bugfixes to the built-in rake helpers
• Fix a bug where shortrefs weren't unique enough and were
  therfore colliding
• Fix a small bug involving checking whether a local git
  clone is up to date
• Correctly handle explicit '=' dependencies with gems
  pinned to a git source
• Fix an issue with Windows-generated lockfiles by reading
  and writing the lockfile in binary mode
• Fix an issue with shelling out to git in Windows by
  using double quotes around paths
• Detect new Rubygems sources in the Gemfile and update
  the lockfile

1.0.0.rc.6 (August 23, 2010)

Features:

• Much better documentation for most of the commands and Gemfile
  format

Bugfixes:

• Don't attempt to create directories if they already exist
• Fix the capistrano task so that it actually runs
• Update the Gemfile template to reference rubygems.org instead
  of :gemcutter
• bundle exec should exit with a non zero exit code when the gem
  binary does not exist or the file is not executable.
• Expand paths in Gemfile relative to the Gemfile and not the current
  working directory.

1.0.0.rc.5 (August 10, 2010)

Features:

• Make the Capistrano task more concise.

Bugfixes:

• Fix a regression with determining whether or not to use sudo
• Allow using the --gemfile flag with the --deployment flag

1.0.0.rc.4 (August 9, 2010)

Features:

• bundle gem NAME command to generate a new gem with Gemfile
• Bundle config file location can be specified by BUNDLE_APP_CONFIG
• Add --frozen to disable updating the Gemfile.lock at runtime
  (default with --deployment)
• Basic Capistrano task now added as 'bundler/capistrano'

Bugfixes:

• Multiple bundler process no longer share a tmp directory
• bundle update GEM always updates dependencies of GEM as well
• Deleting the cache directory no longer causes errors
• Moving the bundle after installation no longer causes git errors
• Bundle path is now correctly remembered on a read-only filesystem
• Gem binaries are installed to Gem.bindir, not #{Gem.dir}/bin
• Fetch gems from vendor/cache, even without --local
• Sort lockfile by platform as well as spec

1.0.0.rc.3 (August 3, 2010)

Features:

• Deprecate --production flag for --deployment, since the former
  was causing confusion with the :production group
• Add --gemfile option to bundle check
• Reduce memory usage of bundle install by 2-4x
• Improve message from bundle check under various conditions
• Better error when a changed Gemfile conflicts with Gemfile.lock

Bugfixes:

• Create bin/ directory if it is missing, then install binstubs
• Error nicely on the edge case of a pinned gem with no spec
• Do not require gems for other platforms
• Update git sources along with the gems they contain

1.0.0.rc.2 (July 29, 2010)

• bundle install path was causing confusion, so we now print
  a clarifying warning. The preferred way to install to a path
  (which will not print the warning) is
  bundle install --path path/to/install.
• bundle install --system installs to the default system
  location ($BUNDLE_PATH or $GEM_HOME) even if you previously
  used bundle install --path
• completely remove --disable-shared-gems. If you install to
  system, you will not be isolated, while if you install to
  another path, you will be isolated from gems installed to
  the system. This was mostly an internal option whose naming
  and semantics were extremely confusing.
• Add a --production option to bundle install:
  • by default, installs to vendor/bundle. This can be
    overridden with the --path option
  • uses --local if vendor/cache is found. This will
    guarantee that Bundler does not attempt to connect to
    Rubygems and will use the gems cached in vendor/cache
    instead
  • Raises an exception if a Gemfile.lock is not found
  • Raises an exception if you modify your Gemfile in development
    but do not check in an updated Gemfile.lock
• Fixes a bug where switching a source from Rubygems to git
  would always say "the git source is not checked out" when
  running bundle install

NOTE: We received several reports of "the git source has not
been checked out. Please run bundle install". As far as we
can tell, these problems have two possible causes:

1. bundle install ~/.bundle in one user, but actually running
   the application as another user. Never install gems to a
   directory scoped to a user (~ or $HOME) in deployment.
2. A bug that happened when changing a gem to a git source.

To mitigate several common causes of (1), please use the
new --production flag. This flag is simply a roll-up of
the best practices we have been encouraging people to use
for deployment.

If you want to share gems across deployments, and you use
Capistrano, symlink release_path/current/vendor/bundle to
release_path/shared/bundle. This will keep deployments
snappy while maintaining the benefits of clean, deploy-time
isolation.

1.0.0.rc.1 (July 26, 2010)

• Fixed a bug with bundle install on multiple machines and git

1.0.0.beta.10 (July 25, 2010)

• Last release before 1.0.0.rc.1
• Added :mri as a valid platform (platforms :mri { gem "ruby-debug" })
• Fix bundle install immediately after modifying the :submodule option
• Don't write to Gemfile.lock if nothing has changed, fixing situations
  where bundle install was run with a different user than the app
  itself
• Fix a bug where other ...

v1.1.pre

Features:

• config system_bindir foo added, works like "-n foo" in your .gemrc file

1.1.pre.9 (Sep 18, 2011)

Features:

• clean will now clean up all old .gem and .gemspec files, cleaning up older pres
• clean will be automatically run after bundle install and update when using --path (#1420, #1425)
• clean now takes a --force option (#1247, #1426)
• clean will clean up cached git dirs in bundle clean (#1390)
• remove deprecations from DSL (#1119)
• autorequire tries directories for gems with dashed names (#1205)
• adds a --paths flag to bundle show to list all the paths of bundled gems (@tiegz, #1360)
• load rubygems plugins in the bundle binary (@tpope, #1364)
• make --standalone respect --path (@cowboyd, #1361)

Bugfixes:

• Fix clean to handle nested gems in a git repo (#1329)
• Fix conflict from revert of benchmark tool (@boffbowsh, #1355)
• Fix fatal error when unable to connect to gem source (#1269)
• Fix outdated to find pre-release gems that are installed. (#1359)
• Fix color for ui. (#1374)
• Fix installing to user-owned system gems on OS X
• Fix caching issue in the resolver (#1353, #1421)
• Fix :github DSL option

1.1.pre.8 (Aug 13, 2011)

Bugfixes:

• Fix bundle check to not print fatal error message (@cldwalker, #1347)
• Fix require_sudo when Gem.bindir isn't writeable (#1352)
• Fix not asking Gemcutter API for dependency chain of git gems in --deployment (#1254)
• Fix install --binstubs when using --path (#1332)

1.1.pre.7 (Aug 8, 2011)

Bugfixes:

• Fixed invalid byte sequence error while installing gem on Ruby 1.9 (#1341)
• Fixed exception when sudo was needed to install gems (@spastorino)

1.1.pre.6 (Aug 8, 2011)

Bugfixes:

• Fix cross repository dependencies (#1138)
• Fix git dependency fetching from API endpoint (#1254)
• Fixes for bundle outdated (@joelmoss, #1238)
• Fix bundle standalone when using the endpoint (#1240)

Features:

• Implement to_ary to avoid calls to method_missing (@tenderlove, #1274)
• bundle clean removes old .gem files (@cldwalker, #1293)
• Correcly identify missing child dependency in error message
• Run pre-install, post-build, and post-install gem hooks for git gems (@warhammerkid, #1120)
• create Gemfile.lock for empty Gemfile (#1218)

1.1.pre.5 (June 11, 2011)

Bugfixes:

• Fix LazySpecification on Ruby 1.9 (@dpiddy, #1232)
• Fix HTTP proxy support (@leobessa, #878)

Features:

• Speed up install --deployment by using the API endpoint
• Support Basic HTTP Auth for the API endpoint (@dpiddy, #1229)
• Add install --full-index to disable the API endpoint, just in case
• Significantly speed up install by removing unneeded gemspec fetches
• outdated command shows outdated gems (@joelmoss, #1130)
• Print gem post install messages (@csquared, #1155)
• Reduce memory use by removing Specification.new inside method_missing (@tenderlove, #1222)
• Allow check --path

1.1.pre.4 (May 5, 2011)

Bugfixes:

• Fix bug that could prevent installing new gems

1.1.pre.3 (May 4, 2011)

Features:

• Add bundle outdated to show outdated gems (@joelmoss)
• Remove BUNDLE_* from Bundler.with_clean_env (@wuputah)
• Add Bundler.clean_system, and clean_exec (@wuputah)
• Use git config for gem author name and email (@krekoten)

Bugfixes:

• Fix error calling Bundler.rubygems.gem_path
• Fix error when Gem.path returns Gem::FS instead of String

1.1.pre.2 (April 28, 2011)

Features:

• Add :github option to Gemfile DSL for easy git repos
• Merge all fixes from 1.0.12 and 1.0.13

1.1.pre.1 (February 2, 2011)

Bugfixes:

• Compatibility with changes made by Rubygems 1.5

1.1.pre (January 21, 2011)

Features:

• Add bundle clean. Removes unused gems from --path directory
• Initial Gemcutter Endpoint API work, BAI Fetching source index
• Added bundle install --standalone
• Ignore Gemfile.lock when building new gems
• Make it possible to override a .gemspec dependency's source in the
  Gemfile

Removed:

• Removed bundle lock
• Removed bundle install
• Removed bundle install --production
• Removed bundle install --disable-shared-gems

v1.0.9

Bugfixes:

• Fix a bug where Bundler.require could remove gems from the load
  path. In Rails apps with a default application.rb, this removed
  all gems in groups other than :default and Rails.env

1.0.8 (January 18, 2011)

Features:

• Allow overriding gemspec() deps with :git deps
• Add --local option to bundle update
• Ignore Gemfile.lock in newly generated gems
• Use less as help pager instead of more
• Run bundle exec rake instead of rake in Capistrano tasks

Bugfixes:

• Fix --no-cache option for bundle install
• Allow Vlad deploys to work without Capistrano gem installed
• Fix group arguments to bundle console
• Allow groups to be loaded even if other groups were loaded
• Evaluate gemspec() gemspecs in their directory not the cwd
• Count on Rake to chdir to the right place in GemHelper
• Change Pathnames to Strings for MacRuby
• Check git process exit status correctly
• Fix some warnings in 1.9.3-trunk (thanks tenderlove)

1.0.7 (November 17, 2010)

Bugfixes:

• Remove Bundler version from the lockfile because it broke
  backwards compatibility with 1.0.0-1.0.5. Sorry. :(

1.0.6 (November 16, 2010)

Bugfixes:

• Fix regression in update that caused long/wrong results
• Allow git gems on other platforms while installing (#579)

Features:

• Speed up install command using various optimizations
• Significantly increase performance of resolver
• Use upcoming Rubygems performance improvements (@tmm1)
• Warn if the lockfile was generated by a newer version
• Set generated gems' homepage to "", so Rubygems will warn

1.0.5 (November 13, 2010)

Bugfixes:

• Fix regression disabling all operations that employ sudo

1.0.4 (November 12, 2010)

Bugfixes:

• Expand relative :paths from Bundler.root (eg ./foogem)
• Allow git gems in --without groups while --frozen
• Allow gem :ref to be a symbol as well as a string
• Fix exception when Gemfile needs a newer Bundler version
• Explanation when the current Bundler version conflicts
• Explicit error message if Gemfile needs newer Bundler
• Ignore an empty string BUNDLE_GEMFILE
• Skeleton gemspec now works with older versions of git
• Fix shell quoting and ref fetching in GemHelper
• Disable colored output in --deployment
• Preserve line endings in lock file

Features:

• Add support for 'mingw32' platform (aka RubyInstaller)
• Large speed increase when Gemfile.lock is already present
• Huge speed increase when many (100+) system gems are present
• Significant expansion of ISSUES, man pages, and docs site
• Remove Open3 from GemHelper (now it works on Windows™®©)
• Allow setting roles in built-in cap and vlad tasks

1.0.3 (October 15, 2010)

Bugfixes:

• Use bitwise or in #hash to reduce the chance of overflow
• bundle update now works with :git + :tag updates
• Record relative :path options in the Gemfile.lock
• :groups option on gem method in Gemfile now works
• Add #platform method and :platform option to Gemfile DSL
• --without now accepts a quoted, space-separated list
• Installing after --deployment with no lock is now possible
• Binstubs can now be symlinked
• Print warning if cache for --local install is missing gems
• Improve output when installing to a path
• The tests all pass! Yay!

1.0.2 (October 2, 2010)

Bugfix:

• Actually include the man pages in the gem, so help works

1.0.1 (October 1, 2010)

Features:

• Vlad deployment recipe, require 'bundler/vlad'
• Prettier bundle graphs
• Improved gem skeleton for bundle gem
• Prompt on file clashes when generating a gem
• Option to generate binary with gem skeleton
• Allow subclassing of GemHelper for custom tasks
• Chdir to gem directory during bundle open

Bugfixes:

• Allow gemspec requirements with a list of versions
• Accept lockfiles with windows line endings
• Respect BUNDLE_WITHOUT env var
• Allow gem "foo", :platform => :jruby
• Specify loaded_from path in fake gemspec
• Flesh out gem_helper tasks, raise errors correctly
• Respect RBConfig::CONFIG['ruby_install_name'] in binstubs

1.0.0 (August 29, 2010)

Features:

• You can now define :bundle_cmd in the capistrano task

Bugfixes:

• Various bugfixes to the built-in rake helpers
• Fix a bug where shortrefs weren't unique enough and were
  therfore colliding
• Fix a small bug involving checking whether a local git
  clone is up to date
• Correctly handle explicit '=' dependencies with gems
  pinned to a git source
• Fix an issue with Windows-generated lockfiles by reading
  and writing the lockfile in binary mode
• Fix an issue with shelling out to git in Windows by
  using double quotes around paths
• Detect new Rubygems sources in the Gemfile and update
  the lockfile

1.0.0.rc.6 (August 23, 2010)

Features:

• Much better documentation for most of the commands and Gemfile
  format

Bugfixes:

• Don't attempt to create directories if they already exist
• Fix the capistrano task so that it actually runs
• Update the Gemfile template to reference rubygems.org instead
  of :gemcutter
• bundle exec should exit with a non zero exit code when the gem
  binary does not exist or the file is not executable.
• Expand paths in Gemfile relative to the Gemfile and not the current
  working directory.

1.0.0.rc.5 (August 10, 2010)

Features:

• Make the Capistrano task more concise.

Bugfixes:

• Fix a regression with determining whether or not to use sudo
• Allow using the --gemfile flag with the --deployment flag

1.0.0.rc.4 (August 9, 2010)

Features:

• bundle gem NAME command to generate a new gem with Gemfile
• Bundle config file location can be specified by BUNDLE_APP_CONFIG
• Add --frozen to disable updating the Gemfile.lock at runtime
  (default with --deployment)
• Basic Capistrano task now added as 'bundler/capistrano'

Bugfixes:

• Multiple bundler process no longer share a tmp directory
• bundle update GEM always updates dependencies of GEM as well
• Deleting the cache directory no longer causes errors
• Moving the bundle after installation no longer causes git errors
• Bundle path is now correctly remembered on a read-only filesystem
• Gem binaries are installed to Gem.bindir, not #{Gem.dir}/bin
• Fetch gems from vendor/cache, even without --local
• Sort lockfile by platform as well as spec

1.0.0.rc.3 (August 3, 2010)

Features:

• Deprecate --production flag for --deployment, since the former
  was causing confusion with the :production group
• Add --gemfile option to bundle check
• Reduce memory usage of bundle install by 2-4x
• Improve message from bundle check under various conditions
• Better error when a changed Gemfile conflicts with Gemfile.lock

Bugfixes:

• Create bin/ directory if it is missing, then install binstubs
• Error nicely on the edge case of a pinned gem with no spec
• Do not require gems for other platforms
• Update git sources along with the gems they contain

1.0.0.rc.2 (July 29, 2010)

• bundle install path was causing confusion, so we now print
  a clarifying warning. The preferred way to install to a path
  (which will not print the warning) is
  bundle install --path path/to/install.
• bundle install --system installs to the default system
  location ($BUNDLE_PATH or $GEM_HOME) even if you previously
  used bundle install --path
• completely remove --disable-shared-gems. If you install to
  system, you will not be isolated, while if you install to
  another path, you will be isolated from gems installed to
  the system. This was mostly an internal option whose naming
  and semantics were extremely confusing.
• Add a --production option to bundle install:
  • by default, installs to vendor/bundle. This can be
    overridden with the --path option
  • uses --local if vendor/cache is found. This will
    guarantee that Bundler does not attempt to connect to
    Rubygems and will use the gems cached in vendor/cache
    instead
  • Raises an exception if a Gemfile.lock is not found
  • Raises an exception if you modify your Gemfile in development
    but do not check in an updated Gemfile.lock
• Fixes a bug where switching a source from Rubygems to git
  would always say "the git source is not checked out" when
  running bundle install

NOTE: We received several reports of "the git source has not
been checked out. Please run bundle install". As far as we
can tell, these problems have two possible causes:

1. bundle install ~/.bundle in one user, but actually running
   the application as another user. Never install gems to a
   directory scoped to a user (~ or $HOME) in deployment.
2. A bug that happened when changing a gem to a git source.

To mitigate several common causes of (1), please use the
new --production flag. This flag is simply a roll-up of
the best practices we have been encouraging people to use
for deployment.

If you want to share gems across deployments, and you use
Capistrano, symlink release_path/current/vendor/bundle to
release_path/shared/bundle. This will keep deployments
snappy while maintaining the benefits of clean, deploy-time
isolation.

1.0.0.rc.1 (July 26, 2010)

• Fixed a bug with bundle install on multiple machines and git

1.0.0.beta.10 (July 25, 2010)

• Last release before 1.0.0.rc.1
• Added :mri as a valid platform (platforms :mri { gem "ruby-debug" })
• Fix bundle install immediately after modifying the :submodule option
• Don't write to Gemfile.lock if nothing has changed, fixing situations
  where bundle install was run with a different user than the app
  itself
• Fix a bug where other platforms were being wiped on bundle update
• Don't ask for root password on bundle install if not needed
• Avoid setting $GEM_HOME where not needed
• First solid pa...

v1.0.8

Features:

• Allow overriding gemspec() deps with :git deps
• Add --local option to bundle update
• Ignore Gemfile.lock in newly generated gems
• Use less as help pager instead of more
• Run bundle exec rake instead of rake in Capistrano tasks

Bugfixes:

• Fix --no-cache option for bundle install
• Allow Vlad deploys to work without Capistrano gem installed
• Fix group arguments to bundle console
• Allow groups to be loaded even if other groups were loaded
• Evaluate gemspec() gemspecs in their directory not the cwd
• Count on Rake to chdir to the right place in GemHelper
• Change Pathnames to Strings for MacRuby
• Check git process exit status correctly
• Fix some warnings in 1.9.3-trunk (thanks tenderlove)

1.0.7 (November 17, 2010)

Bugfixes:

• Remove Bundler version from the lockfile because it broke
  backwards compatibility with 1.0.0-1.0.5. Sorry. :(

1.0.6 (November 16, 2010)

Bugfixes:

• Fix regression in update that caused long/wrong results
• Allow git gems on other platforms while installing (#579)

Features:

• Speed up install command using various optimizations
• Significantly increase performance of resolver
• Use upcoming Rubygems performance improvements (@tmm1)
• Warn if the lockfile was generated by a newer version
• Set generated gems' homepage to "", so Rubygems will warn

1.0.5 (November 13, 2010)

Bugfixes:

• Fix regression disabling all operations that employ sudo

1.0.4 (November 12, 2010)

Bugfixes:

• Expand relative :paths from Bundler.root (eg ./foogem)
• Allow git gems in --without groups while --frozen
• Allow gem :ref to be a symbol as well as a string
• Fix exception when Gemfile needs a newer Bundler version
• Explanation when the current Bundler version conflicts
• Explicit error message if Gemfile needs newer Bundler
• Ignore an empty string BUNDLE_GEMFILE
• Skeleton gemspec now works with older versions of git
• Fix shell quoting and ref fetching in GemHelper
• Disable colored output in --deployment
• Preserve line endings in lock file

Features:

• Add support for 'mingw32' platform (aka RubyInstaller)
• Large speed increase when Gemfile.lock is already present
• Huge speed increase when many (100+) system gems are present
• Significant expansion of ISSUES, man pages, and docs site
• Remove Open3 from GemHelper (now it works on Windows™®©)
• Allow setting roles in built-in cap and vlad tasks

1.0.3 (October 15, 2010)

Bugfixes:

• Use bitwise or in #hash to reduce the chance of overflow
• bundle update now works with :git + :tag updates
• Record relative :path options in the Gemfile.lock
• :groups option on gem method in Gemfile now works
• Add #platform method and :platform option to Gemfile DSL
• --without now accepts a quoted, space-separated list
• Installing after --deployment with no lock is now possible
• Binstubs can now be symlinked
• Print warning if cache for --local install is missing gems
• Improve output when installing to a path
• The tests all pass! Yay!

1.0.2 (October 2, 2010)

Bugfix:

• Actually include the man pages in the gem, so help works

1.0.1 (October 1, 2010)

Features:

• Vlad deployment recipe, require 'bundler/vlad'
• Prettier bundle graphs
• Improved gem skeleton for bundle gem
• Prompt on file clashes when generating a gem
• Option to generate binary with gem skeleton
• Allow subclassing of GemHelper for custom tasks
• Chdir to gem directory during bundle open

Bugfixes:

• Allow gemspec requirements with a list of versions
• Accept lockfiles with windows line endings
• Respect BUNDLE_WITHOUT env var
• Allow gem "foo", :platform => :jruby
• Specify loaded_from path in fake gemspec
• Flesh out gem_helper tasks, raise errors correctly
• Respect RBConfig::CONFIG['ruby_install_name'] in binstubs

1.0.0 (August 29, 2010)

Features:

• You can now define :bundle_cmd in the capistrano task

Bugfixes:

• Various bugfixes to the built-in rake helpers
• Fix a bug where shortrefs weren't unique enough and were
  therfore colliding
• Fix a small bug involving checking whether a local git
  clone is up to date
• Correctly handle explicit '=' dependencies with gems
  pinned to a git source
• Fix an issue with Windows-generated lockfiles by reading
  and writing the lockfile in binary mode
• Fix an issue with shelling out to git in Windows by
  using double quotes around paths
• Detect new Rubygems sources in the Gemfile and update
  the lockfile

1.0.0.rc.6 (August 23, 2010)

Features:

• Much better documentation for most of the commands and Gemfile
  format

Bugfixes:

• Don't attempt to create directories if they already exist
• Fix the capistrano task so that it actually runs
• Update the Gemfile template to reference rubygems.org instead
  of :gemcutter
• bundle exec should exit with a non zero exit code when the gem
  binary does not exist or the file is not executable.
• Expand paths in Gemfile relative to the Gemfile and not the current
  working directory.

1.0.0.rc.5 (August 10, 2010)

Features:

• Make the Capistrano task more concise.

Bugfixes:

• Fix a regression with determining whether or not to use sudo
• Allow using the --gemfile flag with the --deployment flag

1.0.0.rc.4 (August 9, 2010)

Features:

• bundle gem NAME command to generate a new gem with Gemfile
• Bundle config file location can be specified by BUNDLE_APP_CONFIG
• Add --frozen to disable updating the Gemfile.lock at runtime
  (default with --deployment)
• Basic Capistrano task now added as 'bundler/capistrano'

Bugfixes:

• Multiple bundler process no longer share a tmp directory
• bundle update GEM always updates dependencies of GEM as well
• Deleting the cache directory no longer causes errors
• Moving the bundle after installation no longer causes git errors
• Bundle path is now correctly remembered on a read-only filesystem
• Gem binaries are installed to Gem.bindir, not #{Gem.dir}/bin
• Fetch gems from vendor/cache, even without --local
• Sort lockfile by platform as well as spec

1.0.0.rc.3 (August 3, 2010)

Features:

• Deprecate --production flag for --deployment, since the former
  was causing confusion with the :production group
• Add --gemfile option to bundle check
• Reduce memory usage of bundle install by 2-4x
• Improve message from bundle check under various conditions
• Better error when a changed Gemfile conflicts with Gemfile.lock

Bugfixes:

• Create bin/ directory if it is missing, then install binstubs
• Error nicely on the edge case of a pinned gem with no spec
• Do not require gems for other platforms
• Update git sources along with the gems they contain

1.0.0.rc.2 (July 29, 2010)

• bundle install path was causing confusion, so we now print
  a clarifying warning. The preferred way to install to a path
  (which will not print the warning) is
  bundle install --path path/to/install.
• bundle install --system installs to the default system
  location ($BUNDLE_PATH or $GEM_HOME) even if you previously
  used bundle install --path
• completely remove --disable-shared-gems. If you install to
  system, you will not be isolated, while if you install to
  another path, you will be isolated from gems installed to
  the system. This was mostly an internal option whose naming
  and semantics were extremely confusing.
• Add a --production option to bundle install:
  • by default, installs to vendor/bundle. This can be
    overridden with the --path option
  • uses --local if vendor/cache is found. This will
    guarantee that Bundler does not attempt to connect to
    Rubygems and will use the gems cached in vendor/cache
    instead
  • Raises an exception if a Gemfile.lock is not found
  • Raises an exception if you modify your Gemfile in development
    but do not check in an updated Gemfile.lock
• Fixes a bug where switching a source from Rubygems to git
  would always say "the git source is not checked out" when
  running bundle install

NOTE: We received several reports of "the git source has not
been checked out. Please run bundle install". As far as we
can tell, these problems have two possible causes:

1. bundle install ~/.bundle in one user, but actually running
   the application as another user. Never install gems to a
   directory scoped to a user (~ or $HOME) in deployment.
2. A bug that happened when changing a gem to a git source.

To mitigate several common causes of (1), please use the
new --production flag. This flag is simply a roll-up of
the best practices we have been encouraging people to use
for deployment.

If you want to share gems across deployments, and you use
Capistrano, symlink release_path/current/vendor/bundle to
release_path/shared/bundle. This will keep deployments
snappy while maintaining the benefits of clean, deploy-time
isolation.

1.0.0.rc.1 (July 26, 2010)

• Fixed a bug with bundle install on multiple machines and git

1.0.0.beta.10 (July 25, 2010)

• Last release before 1.0.0.rc.1
• Added :mri as a valid platform (platforms :mri { gem "ruby-debug" })
• Fix bundle install immediately after modifying the :submodule option
• Don't write to Gemfile.lock if nothing has changed, fixing situations
  where bundle install was run with a different user than the app
  itself
• Fix a bug where other platforms were being wiped on bundle update
• Don't ask for root password on bundle install if not needed
• Avoid setting $GEM_HOME where not needed
• First solid pass of bundle config
• Add build options
  • bundle config build.mysql --with-mysql-config=/path/to/config

1.0.0.beta.9 (July 21, 2010)

• Fix install failure when switching from a path to git source
• Fix `bundle exec ...