New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bundle update GEMNAME
fails to use latest version
#7176
Comments
Having this same issue with cocoapods. I have no version specified in my Gemfile, but the version used by Bundler is 1.10.2 while the most recent version is 1.15.2. When I execute Gemfile
Gemfile.lock
|
Feel free to try #7558, that should fix this! |
Not sure if any of you ended up trying #7558, but I implemented a better approach now, in case you want to give it a second try! |
Describe the problem as clearly as you can
bundle update GEMNAME
is not installing the latest version of a dependency, even when the dependencies are satisfied.Demo repo: https://github.com/andyw8/temp-bundle-update-issue
Did you try upgrading rubygems & bundler?
Yes:
Which command did you run?
bundle update tapioca
What were you expecting to happen?
Should update
tapioca
tov0.11.12
.What actually happened?
tapioca
version inGemfile.lock
did not change, remains atv0.11.10
.If I explicitly specify
gem "tapioca", "= 0.11.12"
and runbundle update tapioca
then it updates successfully.If not included with the output of your command, run
bundle env
and paste the output belowEnvironment
Bundler Build Metadata
Bundler settings
Gemfile
Gemfile
Gemfile.lock
The text was updated successfully, but these errors were encountered: