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

Bump rspec-rails from 5.1.2 to 6.0.2 #787

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 5, 2023

Bumps rspec-rails from 5.1.2 to 6.0.2.

Changelog

Sourced from rspec-rails's changelog.

6.0.2 / 2023-05-04

Full Changelog

Bug Fixes:

  • Fix ActionView::PathSet when render_views is off for Rails 7.1. (Eugene Kenny, Iliana, #2631)
  • Support Rails 7.1's #fixtures_paths in example groups (removes a deprecation warning). (Nicholas Simmons, #2664)
  • Fix have_enqueued_job to properly detect enqueued jobs when other jobs were performed inside the expectation block. (Slava Kardakov, Phil Pirozhkov, #2573)

6.0.1 / 2022-10-18

Full Changelog

Bug Fixes:

  • Prevent tagged logged support in Rails 7 calling #name. (Jon Rowe, #2625)

6.0.0 / 2022-10-10

Full Changelog

Enhancements:

  • Support Rails 7
  • Template tweaks to remove instance variables from generated specs. (Takuma Ishikawa, #2599)
  • Generators now respects default path configuration option. (@​vivekmiyani, #2508)

Breaking Changes:

  • Drop support for Rails below 6.1
  • Drop support for Ruby below 2.5 (following supported versions of Rails 6.1)
  • Change the order of after_teardown from after to around in system specs to improve compatibility with extensions and Capybara. (Tim Diggins, #2596)

Deprecations:

  • Deprecates integration spec generator (rspec:integration) which was an alias of request spec generator (rspec:request) (Luka Lüdicke, #2374)
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [rspec-rails](https://github.com/rspec/rspec-rails) from 5.1.2 to 6.0.2.
- [Release notes](https://github.com/rspec/rspec-rails/releases)
- [Changelog](https://github.com/rspec/rspec-rails/blob/main/Changelog.md)
- [Commits](rspec/rspec-rails@v5.1.2...v6.0.2)

---
updated-dependencies:
- dependency-name: rspec-rails
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants