Dependabot can't resolve your Ruby dependency files

[dependabot-preview]

Dependabot can't resolve your Ruby dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

Bundler::VersionConflict with message: Bundler could not find compatible versions for gem "actionpack":
  In Gemfile:
    haml-rails (~> 1.0.0) was resolved to 1.0.0, which depends on
      actionpack (>= 4.0.1)

    s3_direct_upload (~> 0.1.6) was resolved to 0.1.6, which depends on
      jquery-fileupload-rails (~> 0.4.1) was resolved to 0.4.7, which depends on
        actionpack (>= 3.1)

    rails (~> 4.2.0) was resolved to 4.2.10, which depends on
      actionpack (= 4.2.10)

    simple_form (~> 3.1.0) was resolved to 3.1.0, which depends on
      actionpack (~> 4.0)

Bundler could not find compatible versions for gem "activemodel":
  In Gemfile:
    paperclip (< 5) was resolved to 4.3.7, which depends on
      activemodel (>= 3.2.0)

    rails (~> 4.2.0) was resolved to 4.2.10, which depends on
      activemodel (= 4.2.10)

    simple_form (~> 3.1.0) was resolved to 3.1.0, which depends on
      activemodel (~> 4.0)

    web-console (< 3.3.1) was resolved to 3.3.0, which depends on
      activemodel (>= 4.2)

Bundler could not find compatible versions for gem "activerecord":
  In Gemfile:
    delayed_job_active_record (~> 4.1.0) was resolved to 4.1.3, which depends on
      activerecord (>= 3.0, < 5.3)

    rails (~> 4.2.0) was resolved to 4.2.10, which depends on
      activerecord (= 4.2.10)

Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    delayed_job_active_record (~> 4.1.0) was resolved to 4.1.3, which depends on
      delayed_job (>= 3.0, < 5) was resolved to 4.1.9, which depends on
        activesupport (>= 3.0, < 6.2)

    factory_bot_rails (~> 4.11.0) was resolved to 4.11.1, which depends on
      factory_bot (~> 4.11.1) was resolved to 4.11.1, which depends on
        activesupport (>= 3.0.0)

    haml-rails (~> 1.0.0) was resolved to 1.0.0, which depends on
      activesupport (>= 4.0.1)

    jbuilder (~> 2.0) was resolved to 2.7.0, which depends on
      activesupport (>= 4.2.0)

    kaminari (~> 1.0) was resolved to 1.1.1, which depends on
      activesupport (>= 4.1.0)

    paperclip (< 5) was resolved to 4.3.7, which depends on
      activesupport (>= 3.2.0)

    rails (~> 4.2.0) was resolved to 4.2.10, which depends on
      activesupport (= 4.2.10)

Bundler could not find compatible versions for gem "i18n":
  In Gemfile:
    rails (~> 4.2.0) was resolved to 4.2.10, which depends on
      activesupport (= 4.2.10) was resolved to 4.2.10, which depends on
        i18n (~> 0.7)

    faker was resolved to 1.9.1, which depends on
      i18n (>= 0.7)

    money (~> 6.7.0) was resolved to 6.7.1, which depends on
      i18n (>= 0.6.4, <= 0.7.0)

Bundler could not find compatible versions for gem "mimemagic":
  In Gemfile:
    paperclip (< 5) was resolved to 4.3.7, which depends on
      mimemagic (= 0.3.0)

Could not find gem 'mimemagic (= 0.3.0)', which is required by gem 'paperclip (< 5)', in any of the sources.

Bundler could not find compatible versions for gem "nokogiri":
  In Gemfile:
    nokogiri (>= 1.6.8.1, <= 1.11.5)

    aws-sdk (~> 1.54.0) was resolved to 1.54.0, which depends on
      aws-sdk-v1 (= 1.54.0) was resolved to 1.54.0, which depends on
        nokogiri (>= 1.4.4)

    creek (~> 1.0.5) was resolved to 1.0.5, which depends on
      nokogiri (~> 1.6.0)

Bundler could not find compatible versions for gem "rack":
  In Gemfile:
    rails (~> 4.2.0) was resolved to 4.2.10, which depends on
      actionpack (= 4.2.10) was resolved to 4.2.10, which depends on
        rack (~> 1.6)

    sass-rails (~> 5.0.0) was resolved to 5.0.7, which depends on
      sprockets (>= 2.8, < 4.0) was resolved to 3.7.2, which depends on
        rack (> 1, < 3)

    devise (>= 4.7.1) was resolved to 4.8.0, which depends on
      warden (~> 1.2.3) was resolved to 1.2.7, which depends on
        rack (>= 1.0)

Bundler could not find compatible versions for gem "railties":
  In Gemfile:
    coffee-rails (~> 4.0.0) was resolved to 4.0.0, which depends on
      railties (>= 4.0.0.beta, < 5.0)

    devise (>= 4.7.1) was resolved to 4.8.0, which depends on
      railties (>= 4.1.0)

    factory_bot_rails (~> 4.11.0) was resolved to 4.11.1, which depends on
      railties (>= 3.0.0)

    haml-rails (~> 1.0.0) was resolved to 1.0.0, which depends on
      railties (>= 4.0.1)

    jquery-rails (~> 4.3.0) was resolved to 4.3.3, which depends on
      railties (>= 4.2.0)

    jquery-ui-rails (~> 6.0.0) was resolved to 6.0.1, which depends on
      railties (>= 3.2.16)

    lodash-rails was resolved to 4.0.0, which depends on
      railties (>= 3.1)

    minitest-rails (< 3) was resolved to 2.1.1, which depends on
      railties (~> 4.1)

    quiet_assets (~> 1.1.0) was resolved to 1.1.0, which depends on
      railties (>= 3.1, < 5.0)

    rails (~> 4.2.0) was resolved to 4.2.10, which depends on
      railties (= 4.2.10)

    react-rails (~> 2.4.0) was resolved to 2.4.7, which depends on
      railties (>= 3.2)

    responders (~> 2.0) was resolved to 2.1.0, which depends on
      railties (>= 4.2.0, < 5)

    sass-rails (~> 5.0.0) was resolved to 5.0.7, which depends on
      railties (>= 4.0.0, < 6)

Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby (~> 2.3.7.0)

    prawn (~> 2.2.0) was resolved to 2.2.2, which depends on
      ttfunk (~> 1.5) was resolved to 1.6.2.1, which depends on
        ruby (~> 2.4)

Bundler could not find compatible versions for gem "thor":
  In Gemfile:
    jquery-rails (~> 4.3.0) was resolved to 4.3.3, which depends on
      thor (>= 0.14, < 2.0)

    rails (~> 4.2.0) was resolved to 4.2.10, which depends on
      railties (= 4.2.10) was resolved to 4.2.10, which depends on
        thor (>= 0.18.1, < 2.0)

    select2-rails (~> 4.0) was resolved to 4.0.3, which depends on
      thor (~> 0.14)

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.