I found an answer here: https://github.com/heroku/heroku-buildpack-ruby
"For non-windows Gemfile.lock files, the --deployment flag will be used. In the case of windows, the Gemfile.lock will be deleted and Bundler will do a full resolve so native gems are handled properly. " On Dec 22, 10:22 am, Vitaliy Khustochka <[email protected]> wrote: > Could it be because I have both ruby and mingw gems in my > Gemfile.lock ? > > On Dec 22, 10:17 am, Vitaliy Khustochka <[email protected]> wrote: > > > > > > > > > It seems to me that some time ago Heroku started to ignore my > > Gemfile.lock which is certainly checked in to the repository. For > > example, when deploying I get a bundler output and among them: > > > Installing kaminari (0.13.0) > > > While in my Gemfile.lock it is `kaminari (0.12.4)` > > > Certainly if I run `heroku run cat Gemfile.lock` it shows an updated > > lock file > > > So could anyone please help am I doing something wrong or the problem > > is on heroku, or it is supposed to work this way? As I already said it > > seems to me it started to happen some time ago. Before that it obeyed > > Gemfile.lock perfectly. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
