To illustrate, the probably won't break anything, similar scenarios can happen that involve much larger jumps.
(see  below for a larger discussion) In order to avoid this problem, when you update a gem, bundler will not update a dependency of that gem if another gem still depends on it. If bundler needs to update a gem that another gem depends on, it will let you know after the update has completed.
The Interne seems vague in giving me a solution to this problem.
Note: This is not a complete, covering every possible case tutorial. If so, feel free to comment and I will try to update the post with other issues and solutions. If you don’t have a good code coverage level and you lack tests, upgrading from Rails 4.2 to Rails 5 might be a big problem.If you’re like most developers, you probably change some generated files, like : Never change generated files.Every time you have to change a default configuration, create an initializer file.Every time you start a new Ruby on Rails project, you use the latest stable released version.You start coding, a process that can take some time (weeks or months, even). The first thing you have to keep in mind is that you do have a better chance by doing small upgrades. there are lots of changes between these releases, with deprecations and even feature removal, but doing it in small doses will make your life way easier.