You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So when I run gemnasium autoupdate, it tries updating that gem, even though I've explicitly locked the version in my Gemfile. This leads to the command taking a long time to execute (#33).
I know changing the default behavior would probably be a bad idea, especially because some people specify gem versions directly in their Gemfile instead of using Gemfile.lock as intended. But maybe some kind of flag that can be passed in order to exclude certain gems from the autoupdate?
The text was updated successfully, but these errors were encountered:
In my
Gemfile
, I've locked the gemactive_model_serializers
to a specific version:While
0.8.3
is an old version, the newer versions are basically different gems, and I'm waiting until a stable1.0.0
release in order to upgrade. The upgrade process for that gem is pretty strange: https://github.com/rails-api/active_model_serializers#release-candidate-please-readSo when I run
gemnasium autoupdate
, it tries updating that gem, even though I've explicitly locked the version in my Gemfile. This leads to the command taking a long time to execute (#33).I know changing the default behavior would probably be a bad idea, especially because some people specify gem versions directly in their
Gemfile
instead of usingGemfile.lock
as intended. But maybe some kind of flag that can be passed in order to exclude certain gems from the autoupdate?The text was updated successfully, but these errors were encountered: