Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ruby - main] New version of rspec-rails (7.1.0) produced dependency conflicts #3077

Closed
wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Nov 10, 2024

👉 This PR is queued up to get rebased by Depfu

We've tried to upgrade a dependency and got errors running Bundler. 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:
    active_model_serializers (~> 0.10.14) was resolved to 0.10.14, which depends on
      actionpack (>= 4.1)

    importmap-rails (~> 1.2, >= 1.2.1) was resolved to 1.2.3, which depends on
      actionpack (>= 6.0.0)

    originator (~> 3.1) was resolved to 3.1, which depends on
      actionpack (>= 4.0)

    rails (~> 7.2.0) was resolved to 7.2.2, which depends on
      actionpack (= 7.2.2)

    rails-controller-testing (~> 1.0) was resolved to 1.0.5, which depends on
      actionpack (>= 5.0.1.rc1)

    rspec-rails (~> 7.1) was resolved to 7.1.0, which depends on
      actionpack (>= 7.0)

    simple_form (>= 4.0, < 6) was resolved to 5.3.1, which depends on
      actionpack (>= 5.2)

Bundler could not find compatible versions for gem "activemodel":
  In Gemfile:
    active_model_serializers (~> 0.10.14) was resolved to 0.10.14, which depends on
      activemodel (>= 4.1)

    rails (~> 7.2.0) was resolved to 7.2.2, which depends on
      activemodel (= 7.2.2)

    rspec-activemodel-mocks (~> 1.0) was resolved to 1.2.1, which depends on
      activemodel (>= 3.0)

    simple_form (>= 4.0, < 6) was resolved to 5.3.1, which depends on
      activemodel (>= 5.2)

    web-console (~> 4.2) was resolved to 4.2.1, which depends on
      activemodel (>= 6.0.0)

Bundler could not find compatible versions for gem "activerecord":
  In Gemfile:
    active_record_query_trace was resolved to 1.8.2, which depends on
      activerecord (>= 6.0.0)

    acts_as_list (>= 0.3, < 2) was resolved to 1.2.3, which depends on
      activerecord (>= 6.1)

    annotate was resolved to 3.2.0, which depends on
      activerecord (< 8.0, >= 3.2)

    awesome_nested_set (~> 3.1, >= 3.7.0) was resolved to 3.7.0, which depends on
      activerecord (< 8.0, >= 4.0.0)

    gutentag (~> 2.2, >= 2.2.1) was resolved to 2.6.2, which depends on
      activerecord (>= 3.2.0)

    originator (~> 3.1) was resolved to 3.1, which depends on
      activerecord (>= 4.0)

    rails (~> 7.2.0) was resolved to 7.2.2, which depends on
      activerecord (= 7.2.2)

    ransack (>= 1.8, < 5.0) was resolved to 4.2.1, which depends on
      activerecord (>= 6.1.5)

Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    acts_as_list (>= 0.3, < 2) was resolved to 1.2.3, which depends on
      activesupport (>= 6.1)

    importmap-rails (~> 1.2, >= 1.2.1) was resolved to 1.2.3, which depends on
      activesupport (>= 6.0.0)

    kaminari (~> 1.1) was resolved to 1.2.2, which depends on
      activesupport (>= 4.1.0)

    rails (~> 7.2.0) was resolved to 7.2.2, which depends on
      activesupport (= 7.2.2)

    rails-controller-testing (~> 1.0) was resolved to 1.0.5, which depends on
      activesupport (>= 5.0.1.rc1)

    ransack (>= 1.8, < 5.0) was resolved to 4.2.1, which depends on
      activesupport (>= 6.1.5)

    rspec-activemodel-mocks (~> 1.0) was resolved to 1.2.1, which depends on
      activesupport (>= 3.0)

    rspec-rails (~> 7.1) was resolved to 7.1.0, which depends on
      activesupport (>= 7.0)

    shoulda-matchers (~> 6.0) was resolved to 6.4.0, which depends on
      activesupport (>= 5.2.0)

    view_component (~> 3.0) was resolved to 3.20.0, which depends on
      activesupport (< 8.1, >= 5.2.0)

Bundler could not find compatible versions for gem "alchemy_cms":
  In Gemfile:
    alchemy_i18n was resolved to 4.2.2, which depends on
      alchemy_cms (>= 8.0.0.a, < 9)

Could not find gem 'alchemy_cms (>= 8.0.0.a, < 9)', which is required by gem 'alchemy_i18n', in rubygems repository https://rubygems.org/ or installed locally.

Bundler could not find compatible versions for gem "railties":
  In Gemfile:
    coffee-rails (>= 4.0, < 6.0) was resolved to 5.0.0, which depends on
      railties (>= 5.2.0)

    factory_bot_rails (~> 6.0) was resolved to 6.4.4, which depends on
      railties (>= 5.0.0)

    importmap-rails (~> 1.2, >= 1.2.1) was resolved to 1.2.3, which depends on
      railties (>= 6.0.0)

    rails (~> 7.2.0) was resolved to 7.2.2, which depends on
      railties (= 7.2.2)

    rails_live_reload (~> 0.3.5) was resolved to 0.3.6, which depends on
      railties

    rspec-rails (~> 7.1) was resolved to 7.1.0, which depends on
      railties (>= 7.0)

What changed?

✳️ rspec-rails (~> 6.1 → ~> 7.1) · Repo · Changelog

Release Notes

7.1.0 (from changelog)

Full Changelog

Enhancements:

  • Improve implicit description for ActionCable matchers have_broadcasted_to / have_broadcast. (Simon Fish, #2795)
  • Comment out infer_spec_type_from_file_location! in newly generated rails_helper.rb files. (Jon Rowe, #2804)
  • Allow turning off active job / mailer argument validation. (Oli Peate, #2808)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot requested a review from a team as a code owner November 10, 2024 12:25
@depfu depfu bot added the depfu label Nov 10, 2024
Copy link

codecov bot commented Nov 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.59%. Comparing base (6b13cc8) to head (8c9e270).
Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3077   +/-   ##
=======================================
  Coverage   96.59%   96.59%           
=======================================
  Files         236      236           
  Lines        6337     6337           
=======================================
  Hits         6121     6121           
  Misses        216      216           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

@tvdeyen
Copy link
Member

tvdeyen commented Nov 18, 2024

@depfu rebase

@depfu depfu bot force-pushed the depfu/update/main/rspec-rails-7.1.0 branch from 187724a to 8c9e270 Compare November 18, 2024 11:24
@tvdeyen tvdeyen closed this Nov 18, 2024
@depfu depfu bot deleted the depfu/update/main/rspec-rails-7.1.0 branch November 18, 2024 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant