When I ran gem bundle the first time, dependencies were resolved, downloaded and installed. Among them was capistrano version 2.5.10. Recently, capistrano 2.5.11 was released, and even though the bundled version satisfies the dependencies, running gem bundle again results in:
Is this expected when running gem bundle without any command arguments? I was under the impression that only gem bundle --update would try to find a newer version that satisfies the dependencies.
Perhaps I am amiss here, but it seems that running
gem bundle
twice with the following Gemfile is not idempotent:When I ran gem bundle the first time, dependencies were resolved, downloaded and installed. Among them was capistrano version 2.5.10. Recently, capistrano 2.5.11 was released, and even though the bundled version satisfies the dependencies, running
gem bundle
again results in:Is this expected when running
gem bundle
without any command arguments? I was under the impression that onlygem bundle --update
would try to find a newer version that satisfies the dependencies.