New version of rspec-rails (3.7.2) produced dependency conflicts

[depfu]

---

Welcome to Depfu 👋

This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.

After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.

Let us know if you have any questions. Thanks so much for giving Depfu a try!

---

⚠️ No CI detected ⚠️

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Our friends at Travis-CI provide excellent service.
• Circle CI are good, too, and have a free plan that will cover basic needs.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

It might be necessary to once deactivate and reactivate your project in Depfu for the CI service to be properly detected.

---

We've tried to upgrade a dependency and got errors running Bundler.

name	version specification	new version
rspec-rails	~> 2.7	3.7.2

It looks like there is a version conflict between two or more dependencies. Depfu doesn't try to solve these, as this would mean to update more than one dependency at a time.

Please take a look at the exact failure to figure out if this is something you need to work on.

The bundler error message was:

Bundler could not find compatible versions for gem "actionpack":
  In Gemfile:
    activeadmin was resolved to 2.0.0.alpha, which depends on
      formtastic (~> 3.1) was resolved to 3.1.5, which depends on
        actionpack (>= 3.2.13)

    activeadmin was resolved to 2.0.0.alpha, which depends on
      inherited_resources (>= 1.7.0) was resolved to 1.8.0, which depends on
        has_scope (~> 0.6) was resolved to 0.7.2, which depends on
          actionpack (>= 4.1)

    activeadmin was resolved to 2.0.0.alpha, which depends on
      inherited_resources (>= 1.7.0) was resolved to 1.8.0, which depends on
        actionpack (<= 5.2, >= 4.2)

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

    ransack was resolved to 1.8.8, which depends on
      actionpack (>= 3.0)

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

    ransack was resolved to 1.8.8, which depends on
      activerecord (>= 3.0)

Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    activeadmin was resolved to 2.0.0.alpha, which depends on
      arbre (>= 1.1.1) was resolved to 1.1.1, which depends on
        activesupport (>= 3.0.0)

    activeadmin was resolved to 2.0.0.alpha, which depends on
      inherited_resources (>= 1.7.0) was resolved to 1.8.0, which depends on
        has_scope (~> 0.6) was resolved to 0.7.2, which depends on
          activesupport (>= 4.1)

    activeadmin was resolved to 2.0.0.alpha, which depends on
      kaminari (>= 1.0.1) was resolved to 1.1.1, which depends on
        activesupport (>= 4.1.0)

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

    ransack was resolved to 1.8.8, which depends on
      activesupport (>= 3.0)

Bundler could not find compatible versions for gem "i18n":
  In Gemfile:
    rails (~> 4.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)

    ransack was resolved to 1.8.8, which depends on
      i18n

Bundler could not find compatible versions for gem "rack":
  In Gemfile:
    rails (~> 4.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)

    capybara was resolved to 3.4.1, which depends on
      rack (>= 1.6.0)

    activeadmin was resolved to 2.0.0.alpha, which depends on
      sprockets (< 4.1, >= 3.0) was resolved to 3.7.2, which depends on
        rack (< 3, > 1)

    devise was resolved to 4.4.3, 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 "rack-test":
  In Gemfile:
    rails (~> 4.0) was resolved to 4.2.10, which depends on
      actionpack (= 4.2.10) was resolved to 4.2.10, which depends on
        rack-test (~> 0.6.2)

    capybara was resolved to 3.4.1, which depends on
      rack-test (>= 0.6.3)

Bundler could not find compatible versions for gem "railties":
  In Gemfile:
    activeadmin was resolved to 2.0.0.alpha, which depends on
      railties (< 5.3, >= 4.2)

    coffee-rails (~> 4.0) was resolved to 4.2.2, which depends on
      railties (>= 4.0.0)

    devise was resolved to 4.4.3, which depends on
      railties (< 6.0, >= 4.1.0)

    activeadmin was resolved to 2.0.0.alpha, which depends on
      inherited_resources (>= 1.7.0) was resolved to 1.8.0, which depends on
        railties (<= 5.2, >= 4.2)

    activeadmin was resolved to 2.0.0.alpha, which depends on
      jquery-rails (>= 4.2.0) was resolved to 4.3.3, which depends on
        railties (>= 4.2.0)

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

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

    rspec-rails (~> 3.7) was resolved to 3.7.2, which depends on
      railties (>= 3.0)

    sass-rails (~> 4.0) was resolved to 4.0.1, which depends on
      railties (< 5.0, >= 4.0.0)

Bundler could not find compatible versions for gem "sprockets":
  In Gemfile:
    activeadmin was resolved to 2.0.0.alpha, which depends on
      sprockets (< 4.1, >= 3.0)

    sass-rails (~> 4.0) was resolved to 4.0.1, which depends on
      sprockets-rails (~> 2.0.0) was resolved to 2.0.1, which depends on
        sprockets (~> 2.8)

What changed?

✳️ rspec-rails ( → 3.7.2) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 15 commits:

• Update version to 3.7.2
• Indent example in the request spec docs (#1909)
• Changelog for #1903 and #1907
• Fix system test screenshots for aggregate failures
• Fix "uninitialized constant Gem" and other Travis errors (#1914)
• Improve doc about Job specs & Rails versions matrix (#1886)
• Fix "character class has duplicated range" warning (#1913)
• Fix failing sanity check spec under latest bundler (#1912)
• Refactor system test integration (delay loading). (#1903)
• Follow updated ruby versions in the matrix (#1906)
• Update Ruby versions in line with other repos
• [FIX-1554] fix fixture_file_upload path resolution (#1880)
• Update FactoryGirl to FactoryBot on README (#1899)
• Check for puma and capybara when defining system tests (#1893)
• Update Changelog for 3.7.1 (#1888)