[ruby] New version of rubocop-rspec (3.7.0) produced dependency conflicts#280
Closed
depfu[bot] wants to merge 1 commit intomainfrom
Closed
[ruby] New version of rubocop-rspec (3.7.0) produced dependency conflicts#280depfu[bot] wants to merge 1 commit intomainfrom
depfu[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
|
Closed in favor of #285. |
This file contains hidden or 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
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.
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:
What changed?
✳️ rubocop-rspec (~> 2.26.1 → ~> 3.7.0) · Repo · Changelog
Release Notes
3.7.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 33 commits:
Merge pull request #2106 from rubocop/releaseRelease v3.7.0Merge pull request #2105 from r7kamura/include-examples-doc-fixFix broken adoc comment in `RSpec/IncludeExamples`Merge pull request #2104 from rubocop/2103Fix a false positive for `RSpec/ExcessiveDocstringSpacing` when receivers are not RSpec methodsMerge pull request #2102 from rubocop/dependabot/github_actions/actions/checkout-5Bump actions/checkout from 4 to 5Merge pull request #2099 from Mth0158/factorybot-wrong-interpretation-of-attribute-as-example-declarationRemove factorybot files inclusion for Metrics/BlockLength copUpdate CHANGELOG.mdUpdate CHANGELOG.mdRemove factorybot inspection for RemoveConst copFix changelog issueExclude all cops from inspecting factorybot files, except if explicitly includedMerge pull request #2100 from lovro-bikic/iterated-expectation-autocorrectionAdd autocorrection support for RSpec/IteratedExpectation for single expectationsMerge pull request #2098 from lovro-bikic/described-class-data-defineDon't register RSpec/DescribedClass offenses within Data.define blockMerge pull request #2097 from lovro-bikic/rspec-dialect-error-matchersAdd support for error matchers to RSpec/DialectMerge pull request #2096 from lovro-bikic/described-class-safetyAdd explanation why RSpec/DescribedClass autocorrection is unsafeMerge pull request #2092 from rubocop/fixinternalFix offenses for `InternalAffairs/ExampleDescription` copMerge pull request #1798 from naveg/define-on-example-groupLeakyConstantDeclaration - allow definitions in explicit namespacesMerge pull request #2089 from yujideveloper/fix/mark-unsafe-autocorrect-for-include_examplesMerge pull request #2091 from lovro-bikic/receive-messages-descriptionAdjust RSpec/ReceiveMessages descriptionMark `RSpec/IncludeExamples` as `SafeAutoCorrect: false`Merge pull request #2082 from rubocop/switch-docs-version-v3.6.0Switch docs version backDepfu 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