Ruby on Rails

On Sat, Sep 9, 2017 at 11:33 AM, Joe Guerra <JGuerra@jginfosys.com> wrote:

> I'm not so sure why bundle update doesn't do this automatically, I'm
> thinking it has to do with the gem file (and if's it locked to a certain
> version).

Of course, the whole point of having versions in the Gemfile is to
lock specific gems to a specific version or range.

> Anyways, updating a few too many broke my code, so instead of trying to
> figure out what I messed up, I reverted back.
>
> So, I guess if it ain't broke don't fix it.

No. Keeping current is essential.

If you fall too far behind, there will be a day when you *must* update
some gem due to a critical security issue -- and you won't be able to
because of some other gem(s) being out of date.

Learning to update and resolve dependencies is just part of the job.

--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
twitter: @hassan
Consulting Availability : Silicon Valley or remote

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yDPY46htxgm%2B8xrAdvHJRjfvJHLiReDpR6t%3DuepJsdSHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.