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:

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.

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 bundle * in a bundle with --disable-shared-gems

Fix bundle * from inside a bundle with --disable-shared-gem

Shim Gem.refresh. This is used by Unicorn

Fix install failure when a path's dependencies changed

1.0.0.beta.8 (July 20, 2010)

Fix a Beta 7 bug involving Ruby 1.9

1.0.0.beta.7 (July 20, 2010, yanked)

Running bundle install twice in a row with a git source always crashed

1.0.0.beta.6 (July 20, 2010, yanked)

Create executables with bundle install --binstubs

You can customize the location (default is app/bin) with --binstubs other/location

Fix a bug where the Gemfile.lock would be deleted even if the update was exited

Fix a bug where cached gems for other platforms were sometimes deleted

Clean up output when nothing was deleted from cache (it previously said
"Removing outdated gems ...")

Improve performance of bundle install if the git gem was already checked out,
and the revision being used already exists locally

Fix bundle show bundler in some cases

Fix bugs with bundle update

Don't ever run git commands at runtime (fixes a number of common passenger issues)

Fixes an obscure bug where switching the source of a gem could fail to correctly
change the source of its dependencies

Support multiple version dependencies in the Gemfile
(gem "rails", ">= 3.0.0.beta1", "<= 3.0.0")

Raise an exception for ambiguous uses of multiple declarations of the same gem
(for instance, with different versions or sources).

Fix cases where the same dependency appeared several times in the Gemfile.lock

Fix a bug where require errors were being swallowed during Bundler.require