Not as such. You are seeing the result of running bundle update without any arguments -- it seeks out updates to every gem in your application. You should actually only run bundle update with arguments unless you have specified a version or version range for every gem in your Gemfile, because you can end up with a combination of gem versions that, while they may _say_ that they are compatible, are not, and have a heck of a time getting back to a running app. Better to say bundle update autoprefixer, which will give you updates for that gem and any of its dependencies. Then run your tests again to make sure everything is still good.
Walter
>
>
> Ralph Shnelvar
>
> --
> 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-ta...@googlegroups.com.
> To post to this group, send email to
rubyonra...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/1835888511.20170707034423%40dos32.com.
> For more options, visit
https://groups.google.com/d/optout.