All Versions
Latest Version
Avg Release Cycle
41 days
Latest Release
1622 days ago

Changelog History
Page 3

  • v1.15.4 Changes

    August 19, 2017

    ๐Ÿ›  Bugfixes:

    • handle file conflicts gracefully in bundle gem (@rafaelfranca, @segiddins)
    • bundler will fail gracefully when the bundle path contains the system path separator (#5485, ajwann)
    • failed gem downloads will be retried consistently across different RubyGems versions (@shayonj)
    • bundle pristine will respect build options while re-building native extensions (@NickLaMuro)
  • v1.15.3 Changes

    July 21, 2017

    ๐Ÿ›  Bugfixes:

    • ensure that empty strings passed to bundle config are serialized & parsed properly (#5881, @segiddins)
    • avoid printing an outdated version warning when running a parseable command (@segiddins)
  • v1.15.2 Changes

    July 17, 2017

    ๐Ÿ”‹ Features:

    • new gemfiles created by bundler will include an explicit github git source that uses https (@segiddins)

    ๐Ÿ›  Bugfixes:

    • inline gemfiles work when BUNDLE_BIN is set (#5847, @segiddins)
    • avoid using the old dependency API when there are no changes to the compact index files (#5373, @greysteil)
    • fail gracefully when the full index serves gemspecs with invalid dependencies (#5797, @segiddins)
    • support installing gemfiles that use eval_gemfile, :path gems with relative paths, and --deployment simultaneously (@NickLaMuro)
    • bundle config will print settings as the type they are interpreted as (@segiddins)
    • respect the no_proxy environment variable when making network requests (#5781, @jakauppila)
    • commands invoked with --verbose will not have default flags printed (@segiddins)
    • allow bundle viz to work when another gem has a requirable grapviz file (#5707, @segiddins)
    • ensure bundler puts activated gems on the $LOAD_PATH in a consistent order (#5696, @segiddins)
  • v1.15.1 Changes

    June 02, 2017

    ๐Ÿ›  Bugfixes:

    • bundle lock --update GEM will fail gracefully when the gem is not in the lockfile (#5693, @segiddins)
    • bundle init --gemspec will fail gracefully when the gemspec is invalid (@colby-swandale)
    • bundle install --force works when the gemfile contains git gems (#5678, @segiddins)
    • bundle env will print well-formed markdown when there are no settings (#5677, @segiddins)
  • v1.15.0 Changes

    May 19, 2017

    This space intentionally left blank.

  • v1.14.6 Changes

    March 03, 2017

    ๐Ÿ›  Bugfixes:

    • avoid undefined constant Bundler::Plugin::API::Source exception (#5409, @segiddins)
    • avoid incorrect warnings about needing to enable specific_platform (@segiddins)
    • fail gracefully when the compact index does not send an ETag (#5463, @olleolleolle)
    • ensure bundle outdated --local shows all outdated gems (#5430, @denniss)
    • fix a case where ruby version requirements could lead to incorrect resolver conflicts (#5425, @segiddins)
  • v1.14.5 Changes

    February 22, 2017

    ๐Ÿ›  Bugfixes:

    • avoid loading all unused gemspecs during bundle exec on RubyGems 2.3+ (@segiddins)
    • improve resolver performance when dependencies have zero or one total possibilities ignoring requirements (#5444, #5457, @segiddins)
    • enable compact index when OpenSSL FIPS mode is enabled but not active (#5433, @wjordan)
    • use github username instead of git name for the github url in bundle gem (#5438, @danielpclark)
    • avoid a TypeError on RubyGems 2.6.8 when no build settings are set for native extensions (@okkez)
    • fail gracefully when the dependency api is missing runtime dependencies for a gem (@segiddins)
    • handle when a platform-specific gem has more dependencies than the ruby platform version (#5339, #5426, @segiddins)
    • allow running bundler on a machine with no home directory where the temporary directory is not writable (#5371, @segiddins)
    • avoid gem version conflicts on openssl using Ruby 2.5 (#5235, @rhenium)
    • fail when installing in frozen mode and the dependencies for gemspec gems have changed without the lockfile being updated (#5264, @segiddins)
  • v1.14.4 Changes

    February 12, 2017

    ๐Ÿ›  Bugfixes:

    • fail gracefully when attempting to overwrite an existing directory with bundle gem (#5358, @nodo)
    • fix a resolver bug that would cause bundler to report conflicts that it could resolve (#5359, #5362, @segiddins)
    • set native extension build arguments for git gems (#5401, @segiddins)
    • fix the suggested bundle lock command printed when a dependency is unused on any platform (@5t111111)
    • ensure the version passed to ruby in the Gemfile is valid during Gemfile parsing (#5380, @segiddins)
    • show bundle inject usage when too many arguments are passed (#5384, @Shekharrajak)
    • stop bundle show --outdated from implicitly running bundle update (#5375, @colby-swandale)
    • allow the temporary home directory fallback to work for multiple users (@svoop)
  • v1.14.3 Changes

    January 24, 2017

    ๐Ÿ›  Bugfixes:

    • fix the resolver attempting to activate ruby-platform gems when the bundle is only for other platforms (#5349, #5356, @segiddins)
    • avoid re-resolving a locked gemfile that uses gemspec and includes development dependencies (#5349, @segiddins)
  • v1.14.2 Changes

    January 22, 2017

    ๐Ÿ›  Bugfixes:

    • fix using force_ruby_platform on windows (#5344, @segiddins)
    • fix an incorrect version conflict error when using gemspec on multiple platforms (#5340, @segiddins)