Bundler: always use latest revision of git branch in Gemfile

Question

I have a Gemfile with a private git repo in the following format:

gem 'magic_beans', :git => "git@git.example.com:magic_beans.git', :branch => 'super_beans'

When I bundle install, the Gemfile.lock locks it to a specific SHA revision.

Can I get bundler to always check and use the latest SHA commit and/or update the Gemfile.lock? Notice that when I push updates to the super_beans branch I am not modifying the gem version.

Ideally, every time I run bundle it would check upstream git repo for a newer SHA revision of the branch.

score 24 · Accepted Answer · answered Nov 30 '11 at 10:30

24

This isn't how bundler works. The point is to allow seamless versioning of dependencies. (particularly so you know exactly what version of the code is deployed at any given time).

If want the latest version, you should just run.

bundle update magic_beans

This is exactly the same functionality as if you just say

gem "rails"

I'd suggest though, if you have a range of specific things you want to update then add a custom binary (say an executable file named bundle_update)

#!/usr/bin/env bash
bundle install
bundle update magic_beans

Then just do a ./bundle_update when you want to update these things.

answered Nov 30 '11 at 10:30

Matthew Rudy

16,724
3
46
44

If I change `:git` to use a `:path` instead, `bundle install` happily uses the newest SHA each time. I'll just keep using `bundle update`, but I don't think this is necessarily the ideal solution. After all, in my Gemfile I'm not scoping to a `:revision` but a `:branch`. Thanks for the input! – pithyless Nov 30 '11 at 15:09
1

I know this is very old, but setting a `:path` always updates because it loads from a directory, not from a git repository or remote gem. `:path` is great for developing two projects together locally, but breaks down once you start collaborating. – Matthew Rudy Jul 11 '13 at 22:55

score 1 · Answer 2 · answered Feb 11 '15 at 07:45

1

After searching through the documents I finally found the magic way to do this:

bundle update magic_beans --source magic_beans

That is to update the magic_beans gem only, but not to touch other locked gems. The doc about this is: http://bundler.io/man/bundle-update.1.html

answered Feb 11 '15 at 07:45

Michael Yin

1,764
13
13

The first `magic_beans` is not necessary. You can just do `bundle update --source magic_beans`. – lukeasrodgers Apr 01 '15 at 20:41

score 1 · Answer 3 · edited Jun 20 '20 at 09:12

1

You can run bundle update to update all or specific gems to their latest available version, as stated in the docs.

Would that help?

edited Jun 20 '20 at 09:12

Community

1
1

answered Nov 30 '11 at 10:30

leonardoborges

5,579
1
24
26

1

I guess if app and gem repos both belongs to you, and the gem undergoes lots of small changes, it is painful to also do a commit on the main app to point to the latest commit all the time. – lulalala Aug 15 '13 at 06:19

score 0 · Answer 4 · answered Jun 11 '18 at 18:35

0

delete .gemlock is what worked for me :/

answered Jun 11 '18 at 18:35

Fabián Contreras

43
1
6

Bundler: always use latest revision of git branch in Gemfile

4 Answers4