Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
tag: 1.0.0.beta.2
Fetching contributors…

Cannot retrieve contributors at this time

307 lines (207 sloc) 10.116 kB

0.10.0

  • No bundle lock command. Locking happens automatically on install or update
  • No .bundle/environment.rb. Require 'bundler/setup' instead.
  • $BUNDLE_HOME defaults to $GEM_HOME instead of ~/.bundle
  • Remove lockfiles generated by 0.9

0.9.26

Features:

  • error nicely on incompatible 0.10 lockfiles

0.9.25 (May 3, 2010)

Bugfixes:

  • explicitly coerce Pathname objects to Strings for Ruby 1.9
  • fix some newline weirdness in output from install command

0.9.24 (April 22, 2010)

Features:

  • fetch submodules for git sources
  • limit the bundled version of bundler to the same as the one installing
  • force relative paths in git gemspecs to avoid raising Gem::NameTooLong
  • serialize GemCache sources correctly, so locking works
  • raise Bundler::GemNotFound instead of calling exit! inside library code
  • Rubygems 1.3.5 compatibility for the adventurous, not supported by me :)

Bugfixes:

  • don't try to regenerate environment.rb if it is read-only
  • prune outdated gems with the platform "ruby"
  • prune cache without errors when there are directories or non-gem files
  • don't re-write environment.rb if running after it has been loaded
  • do not monkeypatch Specification#load_paths twice when inside a bundle

0.9.23 (April 20, 2010)

Bugfixes:

  • cache command no longer prunes gems created by an older rubygems version
  • cache command no longer prunes gems that are for other platforms

0.9.22 (April 20, 2010)

Features:

  • cache command now prunes stale .gem files from vendor/cache
  • init --gemspec command now generates development dependencies
  • handle Polyglot's changes to Kernel#require with Bundler::ENV_LOADED (#287)
  • remove .gem files generated after installing a gem from a :path (#286)
  • improve install/lock messaging (#284)

Bugfixes:

  • ignore cached gems that are for another platform (#288)
  • install Windows gems that have no architecture set, like rcov (#277)
  • exec command while locked now includes the bundler lib in $LOAD_PATH (#293)
  • fix the rake install task
  • add GemspecError so it can be raised without (further) error (#292)
  • create a parent directory before cloning for git 1.5 compatibility (#285)

0.9.21 (April 16, 2010)

Bugfixes:

  • don't raise 'omg wtf' when lockfile is outdated

0.9.20 (April 15, 2010)

Features:

  • load YAML format gemspecs
  • no backtraces when calling Bundler.setup if gems are missing
  • no backtraces when trying to exec a file without the executable bit

Bugfixes:

  • fix infinite recursion in Bundler.setup after loading a bundled Bundler gem
  • request install instead of lock when env.rb is out of sync with Gemfile.lock

0.9.19 (April 12, 2010)

Features:

  • suggest bundle install --relock when the Gemfile has changed (#272)
  • source support for Rubygems servers without prerelease gem indexes (#262)

Bugfixes:

  • don't set up all groups every time Bundler.setup is called while locked (#263)
  • fix #full_gem_path for git gems while locked (#268)
  • eval gemspecs at the top level, not inside the Bundler class (#269)

0.9.18 (April 8, 2010)

Features:

  • console command that runs irb with bundle (and optional group) already loaded

Bugfixes:

  • Bundler.setup now fully disables system gems, even when unlocked (#266, #246)
    • fixes Yard, which found plugins in Gem.source_index that it could not load
    • makes behaviour of Bundler.require consistent between locked and unlocked loads

0.9.17 (April 7, 2010)

Features:

  • Bundler.require now calls Bundler.setup automatically
  • Gem::Specification#add_bundler_dependencies added for gemspecs

Bugfixes:

  • Gem paths are not longer duplicated while loading bundler
  • exec no longer duplicates RUBYOPT if it is already set correctly

0.9.16 (April 3, 2010)

Features:

  • exit gracefully on INT signal
  • resolver output now indicates whether remote sources were checked
  • print error instead of backtrace when exec cannot find a binary (#241)

Bugfixes:

  • show, check, and open commands work again while locked (oops)
  • show command for git gems
    • outputs branch names other than master
    • gets the correct sha from the checkout
    • doesn't print sha twice if :ref is set
  • report errors from bundler/setup.rb without backtraces (#243)
  • fix Gem::Spec#git_version to not error on unloaded specs
  • improve deprecation, Gemfile, and command error messages (#242)

0.9.15 (April 1, 2010)

Features:

  • use the env_file if possible instead of doing a runtime resolve
    • huge speedup when calling Bundler.setup while locked
    • ensures bundle exec is fast while locked
    • regenerates env_file if it was generated by an older version
  • update cached/packed gems when you update gems via bundle install

Bugfixes:

  • prep for Rubygems 1.3.7 changes
  • install command now pulls git branches correctly (#211)
  • raise errors on invalid options in the Gemfile

0.9.14 (March 30, 2010)

Features:

  • install command output vastly improved
    • installation message now accurate, with 'using' and 'installing'
    • bundler gems no longer listed as 'system gems'
  • show command output now includes sha and branch name for git gems
  • init command now takes --gemspec option for bootstrapping gem Gemfiles
  • Bundler.with_clean_env for shelling out to ruby scripts
  • show command now aliased as 'list'
  • VISUAL env var respected for GUI editors

Bugfixes:

  • exec command now finds binaries from gems with no gemspec
  • note source of Gemfile resolver errors
  • don't blow up if git urls are changed

0.9.13 (March 23, 2010)

Bugfixes:

  • exec command now finds binaries from gems installed via :path
  • gem dependencies are pulled in even if their type is nil
  • paths with spaces have double-quotes to work on Windows
  • set GEM_PATH in environment.rb so generators work with Rails 2

0.9.12 (March 17, 2010)

  • refactoring, internal cleanup, more solid specs

Features:

  • check command takes a --without option
  • check command exits 1 if the check fails

Bugfixes:

  • perform a topological sort on resolved gems (#191)
  • gems from git work even when paths or repos have spaces (#196)
  • Specification#loaded_from returns a String, like Gem::Specification (#197)
  • specs eval from inside the gem directory, even when locked
  • virtual gemspecs are now saved in environment.rb for use when loading
  • unify the Installer's local index and the runtime index (#204)

0.9.11 (March 9, 2010)

  • added roadmap with future development plans

Features:

  • install command can take the path to the gemfile with --gemfile (#125)
  • unknown command line options are now rejected (#163)
  • exec command hugely sped up while locked (#177)
  • show command prints the install path if you pass it a gem name (#148)
  • open command edits an installed gem with $EDITOR (#148)
  • Gemfile allows assigning an array of groups to a gem (#114)
  • Gemfile allows :tag option on :git sources
  • improve backtraces when a gemspec is invalid
  • improve performance by installing gems from the cache if present

Bugfixes:

  • normalize parameters to Bundler.require (#153)
  • check now checks installed gems rather than cached gems (#162)
  • don't update the gem index when installing after locking (#169)
  • bundle parenthesises arguments for 1.8.6 (#179)
  • gems can now be assigned to multiple groups without problems (#135)
  • fix the warning when building extensions for a gem from git with Rubygems 1.3.6
  • fix a Dependency.to_yaml error due to accidentally including sources and groups
  • don't reinstall packed gems
  • fix gems with git sources that are private repositories

0.9.10 (March 1, 2010)

  • depends on Rubygems 1.3.6

Bugfixes:

  • support locking after install --without
  • don't reinstall gems from the cache if they're already in the bundle
  • fixes for Ruby 1.8.7 and 1.9

0.9.9 (February 25, 2010)

Bugfixes:

  • don't die if GEM_HOME is an empty string
  • fixes for Ruby 1.8.6 and 1.9

0.9.8 (February 23, 2010)

Features:

  • pack command which both caches and locks
  • descriptive error if a cached gem is missing
  • remember the --without option after installing
  • expand paths given in the Gemfile via the :path option
  • add block syntax to the git and group options in the Gemfile
  • support gems with extensions that don't admit they depend on rake
  • generate gems using gem build gemspec so git gems can have native extensions
  • print a useful warning if building a gem fails
  • allow manual configuration via BUNDLE_PATH

Bugfixes:

  • eval gemspecs in the gem directory so relative paths work
  • make default spec for git sources valid
  • don't reinstall gems that are already packed

0.9.7 (February 17, 2010)

Bugfixes:

  • don't say that a gem from an excluded group is "installing"
  • improve crippling rubygems in locked scenarios

0.9.6 (February 16, 2010)

Features:

  • allow String group names
  • a number of improvements in the documentation and error messages

Bugfixes:

  • set SourceIndex#spec_dirs to solve a problem involving Rails 2.3 in unlocked mode
  • ensure Rubygems is fully loaded in Ruby 1.9 before patching it
  • fix bundle install for a locked app without a .bundle directory
  • require gems in the order that the resolver determines
  • make the tests platform agnostic so we can confirm that they're green on JRuby
  • fixes for Ruby 1.9

0.9.5 (Feburary 12, 2010)

Features:

  • added support for :path => "relative/path"
  • added support for older versions of git
  • added bundle install --disable-shared-gems
  • Bundler.require fails silently if a library does not have a file on the load path with its name
  • Basic support for multiple rubies by namespacing the default bundle path using the version and engine

Bugfixes:

  • if the bundle is locked and .bundle/environment.rb is not present when Bundler.setup is called, generate it
  • same if it's not present with bundle check
  • same if it's not present with bundle install
Jump to Line
Something went wrong with that request. Please try again.