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

chore(deps): update dependency rspec-rails to v7 #486

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 2, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
rspec-rails (changelog) "~> 6.1.0" -> "~> 7.1.0" age adoption passing confidence

Release Notes

rspec/rspec-rails (rspec-rails)

v7.1.0

Compare Source

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)

v7.0.2

Compare Source

Full Changelog

Bug Fixes:

  • Fix issue with have_enqueued_mail when jobs were incorrectly matched due
    to refactoring in #​2780. (David Runger, #​2793)

v7.0.1

Compare Source

Full Changelog

Bug Fixes:

  • Remove mutation of Rails constant in favour of public api. (Petrik de Heus, #​2789)
  • Cleanup Rails scaffold for unsupported versions. (Matt Jankowski, #​2790)
  • Remove deprecated scaffold that was unintentionally included in 7.0.0
    (Jon Rowe, #​2791)

v7.0.0

Compare Source

Full Changelog

Enhancements:

  • Change default driver for system specs on Rails 7.2 to match its default.
    (Steve Polito, #​2746)
  • Verify ActiveJob arguments by comparing to the method signature. (Oli Peate, #​2745)
  • Add suggestion to rails_helper.rb to skip when not in test mode. (Glauco Custódio, #​2751)
  • Add at_priority qualifier to have_enqueued_job set of matchers. (mbajur, #​2759)
  • Add spec directories to rails stats on Rails main / 8.0.0. (Petrik de Heus, #​2781)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Jan 2, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: audiences/Gemfile.lock
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...

Could not find compatible versions

Because rails >= 6.1.7, < 6.1.7.1 depends on railties = 6.1.7
  and rails >= 6.1.7.1, < 6.1.7.2 depends on railties = 6.1.7.1,
  rails >= 6.1.7, < 6.1.7.2 requires railties = 6.1.7 OR = 6.1.7.1.
And because rails >= 6.1.7.2, < 6.1.7.3 depends on railties = 6.1.7.2
  and rails >= 6.1.7.3, < 6.1.7.4 depends on railties = 6.1.7.3,
rails >= 6.1.7, < 6.1.7.4 requires railties = 6.1.7 OR = 6.1.7.1 OR = 6.1.7.2
OR = 6.1.7.3.
And because rails >= 6.1.7.4, < 6.1.7.5 depends on railties = 6.1.7.4
  and rails >= 6.1.7.5, < 6.1.7.6 depends on railties = 6.1.7.5,
rails >= 6.1.7, < 6.1.7.6 requires railties = 6.1.7 OR = 6.1.7.1 OR = 6.1.7.2
OR = 6.1.7.3 OR = 6.1.7.4 OR = 6.1.7.5.
And because rails >= 6.1.7.6, < 6.1.7.7 depends on railties = 6.1.7.6
  and rails >= 6.1.7.7, < 6.1.7.8 depends on railties = 6.1.7.7,
rails >= 6.1.7, < 6.1.7.8 requires railties = 6.1.7 OR = 6.1.7.1 OR = 6.1.7.2
OR = 6.1.7.3 OR = 6.1.7.4 OR = 6.1.7.5 OR = 6.1.7.6 OR = 6.1.7.7.
And because rails >= 6.1.7.8, < 6.1.7.9 depends on railties = 6.1.7.8
  and rails >= 6.1.7.9, < 6.1.7.10 depends on railties = 6.1.7.9,
rails >= 6.1.7, < 6.1.7.10 requires railties = 6.1.7 OR = 6.1.7.1 OR = 6.1.7.2
OR = 6.1.7.3 OR = 6.1.7.4 OR = 6.1.7.5 OR = 6.1.7.6 OR = 6.1.7.7 OR = 6.1.7.8 OR
= 6.1.7.9.
And because rails >= 6.1.7.10, < 7.0.0.alpha1 depends on railties = 6.1.7.10
  and rspec-rails >= 7.0.0 depends on railties >= 7.0,
  rspec-rails >= 7.0.0 is incompatible with rails >= 6.1.7, < 7.0.0.alpha1.
So, because Gemfile depends on rails ~> 6.1.7.0
  and Gemfile depends on rspec-rails ~> 7.1.0,
  version solving has failed.

@renovate renovate bot force-pushed the renovate/rspec-rails-7.x branch from 0f0a0dd to 5aab63a Compare January 7, 2025 14:44
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 24 hours if no further activity occurs.
If this change is desirable, please accelerate completing it. If it is not, please close the PR. If you're blocked on something, please ensure there's a reference to this PR in a story on your team's board so the team will follow up, and consider closing the PR for now.
Please do not artificially extend the deadline with a dummy comment. If necessary, provide a status update, such as "this change is being actively tested".
Thank you for your contributions and your collaboration in reducing WIP and cycle time.

@github-actions github-actions bot added the Stale label Jan 11, 2025
@github-actions github-actions bot closed this Jan 12, 2025
@github-actions github-actions bot deleted the renovate/rspec-rails-7.x branch January 12, 2025 21:26
Copy link
Contributor Author

renovate bot commented Jan 12, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 7.x releases. But if you manually upgrade to 7.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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.

0 participants