Update rubocop-rspec 2.29.1 → 2.29.2 (patch) #3376
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
|
Sorry, but the merge failed with:
|
hennevogel
approved these changes
May 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.29.1 → 2.29.2) · Repo · Changelog
Release Notes
2.29.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 13 commits:
Merge pull request #1875 from rubocop/releaseBump to v2.29.1Merge pull request #1873 from rubocop/rubocop-offensesFix some rubocop offensesMerge pull request #1871 from K-S-A/masterFix changelogRSpec/RepeatedSubjectCall: do not report if subject is an argument to a function callMerge pull request #1869 from rubocop/improve-releaseImprove release workflowMerge pull request #1867 from hasghari/range-bugFix bug with range in RepeatedIncludeExample copMerge pull request #1864 from rubocop/improve-publish-workflowPublishing: Only push antora.yml if it's changed✳️ rubocop (1.63.4 → 1.63.5) · Repo · Changelog
Release Notes
1.63.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 22 commits:
Cut 1.63.5Update ChangelogMerge pull request #12890 from koic/add_ostruct_to_gemfileWorkaround for Ruby's warning in YARDMerge pull request #12886 from koic/suppress_interrupt_exception_for_lspFix a build errorFix docs for `Style/SpecialGlobalVars` `use_builtin_english_names`Suppress `Interrupt` exception for LSPCorrect some example descriptionsMerge pull request #12882 from nekketsuuu/nekketsuuu-case-in-commentMerge pull request #12881 from fatkodima/fix-numeric_predicate-autocorrectFix `Layout/CommentIndentation` for comment-only pattern matchingFix incorrect autocorrect when `Style/NumericPredicate` is used with negationsAdd documentation and log information for enabling YJIT in LSPAdd a forgotten period at the end of some offense messageMerge pull request #12877 from koic/fix_an_error_for_layout_first_array_element_indentationFix an infinite loop error for `Layout/FirstArgumentIndentation`Merge pull request #12874 from koic/fix_an_error_for_metrics_block_length[Fix #12873] Fix an error for `Metrics/BlockLength`[Docs] Tweak cops_layout_footer.adocUse `require_relative`Reset the docs versionRelease Notes
2.9.1 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
Release v2.9.1Unify CHANGELOG formattingSimplify path slightlyMerge pull request #90 from koic/use_require_relativeUse `require_relative` in the Regexp::Parser codebaseDepfu 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