Upgrading Bundler version on Heroku
I need an updated version of the bundler on my heroku app (cedar 14) and I have seen no reason why I cannot. I am stuck on 1,6,6 which is a couple of months old and I need the most up-to-date version.
I need to specify a parameter source:
for one of my gems and the earlier version of bundler doesn't allow that. Also, the run heroku run gem update bundler
updates successfully, but 'heroku run bundle -v' gives 1.6.6.
Why?
source to share
You can change the vendor version by pointing Ruby Buildpack to Heroku:
If you see that a different version of Bundler is in use by yours than indicated in the Ruby support article, your application can be configured to use the upstream Ruby buildpack for deployment.
To check which buildpack is configured use the buildkacks heroku command:
> heroku buildpacks
> === hidden-temple-25627 Buildpack URL https://github.com/heroku/heroku-buildpack-ruby.git
The sample output shows that an unreleased version of buildpack is in use. To upgrade to a supported version, install buildpack as follows:
heroku buildpacks: set heroku / ruby Setpack set. The next set on hidden-temple-25627 will use a hero / ruby. Run git push hero master to build new version using this buildpack.
You can check that the new buildpack is installed by typing:
> heroku buildpacks
> === hidden-temple-25627 Buildpack URL heroku/ruby
Another reason your application cannot use the currently supported Bundler Version is if it is configured to deploy using a different buildpack url. This will happen if BUILDPACK_URL config var is set.
> heroku config:get BUILDPACK_URL BUILDPACK_URL:
> https://github.com/heroku/heroku-buildpack-ruby.git
If you see any value, then you are using a custom collector. If this value is set to "multi buildpack", for example https://github.com/heroku/heroku-buildpack-multi , then you will need to check the .buildpacks file to see which buildpacks are used in your deployment. If you are using this deployment method, we recommend that you follow the directions in the Using Multiple Assemblies section for the Application article instead.
The officially deployed Ruby buildpack sometimes lags behind the master by a few days.
Also, it cannot be configured directly:
Why customize the Bundler version?
Different Bundler versions have different known bugs and in slightly different ways. The Bundler version on Heroku is carefully curated. A balance needs to be found between support for the new Bundler features and stability. The work we put into curating the Bundler version ensures maximum stability and avoids deprecation and Bundler notification loops as they change or how bug fixes or security issues are fixed by Heroku.
The Ruby experience on Heroku is provided by the Heroku Ruby Buildpack. It is a tool that installs the Bundler version and runs all the commands needed to configure your application. buildpack relies on public Bundler exhibits. this has been tested and known to work against the currently listed Bundler version. If you took a modern buildpack and used it from an older version of the bundle, you will probably see unpredictable results.
source to share