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

Update rubocop-rspec 2.27.1 → 2.29.1 (minor) #3362

Merged
merged 1 commit into from Apr 16, 2024

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Apr 11, 2024

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ rubocop-rspec (2.27.1 → 2.29.1) · Repo · Changelog

Release Notes

2.29.1

  • Fix an error in the default configuration. (@ydah)

2.29.0

  • Fix an autocorrect error for RSpec/ExpectActual. (@bquorning)
  • Add new RSpec/UndescriptiveLiteralsDescription cop. (@ydah)
  • Add new RSpec/EmptyOutput cop. (@bquorning)

2.28.0

  • Extract RSpec Rails cops to a separate repository, rubocop-rspec_rails. The rubocop-rspec_rails repository is a dependency of rubocop-rspec and the cops related to rspec-rails are aliased (RSpec/Rails/Foo == RSpecRails/Foo) until v3.0 is released, so the change will be invisible to users until then. (@ydah)

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

Commits

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

✳️ rubocop (1.63.0 → 1.63.2) · Repo · Changelog

Release Notes

1.63.1

Bug fixes

  • #12828: Fix a false positive for Lint/AssignmentInCondition if assigning inside a method call. (@earlopain)
  • #12823: Fixed "uninitialized constant RuboCop::Lockfile::Bundler", caused when running RuboCop without bundler exec on codebases that use rubocop-rails. (@amomchilov)

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

Commits

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

🆕 rubocop-rspec_rails (added, 2.28.3)


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 added the depfu Automatic PRs to update gems label Apr 11, 2024
@hennevogel
Copy link
Member

@depfu rebase

@depfu depfu bot force-pushed the depfu/update/rubocop-rspec-2.29.1 branch from af7864a to 9f99279 Compare April 16, 2024 11:36
Copy link
Contributor Author

depfu bot commented Apr 16, 2024

Sorry, but the merge failed with:

At least 1 approving review is required by reviewers with write access. You're not authorized to push to this branch. Visit https://docs.github.com/articles/about-protected-branches/ for more information.

@hennevogel hennevogel merged commit 11aed6d into master Apr 16, 2024
8 checks passed
@depfu depfu bot deleted the depfu/update/rubocop-rspec-2.29.1 branch April 16, 2024 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
depfu Automatic PRs to update gems
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant