massive deprecation warning on rails 5.1

[BranLiang]

DEPRECATION WARNING: The behavior of changed_attributes inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after save returned (e.g. the opposite of what it returns now). To maintain the current behavior, use saved_changes.transform_values(&:first) instead. (called from block (2 levels) in <top (required)> at /home/bran/Desktop/alexandria/spec/requests/books_spec.rb:4)
DEPRECATION WARNING: The behavior of changes inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after save returned (e.g. the opposite of what it returns now). To maintain the current behavior, use saved_changes instead. (called from block (2 levels) in <top (required)> at /home/bran/Desktop/alexandria/spec/requests/books_spec.rb:4)
DEPRECATION WARNING: The behavior of changed inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after save returned (e.g. the opposite of what it returns now). To maintain the current behavior, use saved_changes.keys instead. (called from block (2 levels) in <top (required)> at /home/bran/Desktop/alexandria/spec/requests/books_spec.rb:4)
DEPRECATION WARNING: The behavior of attribute_change inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after save returned (e.g. the opposite of what it returns now). To maintain the current behavior, use saved_change_to_attribute instead. (called from block (2 levels) in <top (required)> at /home/bran/Desktop/alexandria/spec/requests/books_spec.rb:4)
DEPRECATION WARNING: The behavior of attribute_changed? inside of after callbacks will be changing in the next version of Rails. The new return value will reflect the behavior of calling the method after save returned (e.g. the opposite of what it returns now). To maintain the current behavior, use saved_change_to_attribute? instead. (called from block (2 levels) in <top (required)> at /home/bran/Desktop/alexandria/spec/requests/books_spec.rb:4)

[Borzik]

In case someone will face this issue while upgrading to Rails 5.1: it is actually caused by carrierwave gem, not this one. Using gem 'carrierwave', '~> 1.1.0' fixed it for me.

[y9v]

@Borzik thank you! I'm closing this issue