This repository was archived by the owner on Jun 13, 2023. It is now read-only.
[ruby] New version of rubocop-rspec (2.19.0) produced dependency conflicts#340
Closed
depfu[bot] wants to merge 1 commit into
Closed
[ruby] New version of rubocop-rspec (2.19.0) produced dependency conflicts#340depfu[bot] wants to merge 1 commit into
depfu[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Closed in favor of #349. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.15.0 → ~> 2.19.0) · Repo · Changelog
Release Notes
2.19.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 56 commits:
Merge pull request #1590 from rubocop/releaseBump version to v2.19.0Merge pull request #1575 from ydah/refactor-skipped-or-pendingMerge pull request #1589 from ydah/ydah/fix-1588Refactor and adding a common matcher in SkipOrPending moduleFix an incorrect autocorrect for `RSpec/VerifiedDoubleReference` when namespaced classMerge pull request #1586 from r7kamura/feature/internal-affairsAuto-correct `InternalAffairs/LocationExpression` offensesMerge pull request #1585 from ydah/fix-ProcessedSourceBufferNameCorrect `InternalAffairs/ProcessedSourceBufferName` copMerge pull request #1581 from rubocop/sunset-_pattern-helpersAdd deprecation warning and a changelog entryPrepare _pattern abstraction for retirementMerge pull request #1580 from ydah/ci_against_jruby_9_4Merge pull request #1556 from ydah/extract_locationChange to ignore `example?`, `hook?`, `let?`, `include?` and `subject?` matchers with `RSpec` receiversCI against JRuby 9.4 instead of JRuby 9.3Merge pull request #1579 from ydah/enable-some-new-copsEnable Style/RedundantStringEscapeEnable Style/RedundantHeredocDelimiterQuotes and fix offensesExtract Location module as mixinMerge pull request #1577 from ydah/not-use-comment_lineUse `line_with_comment?` instead of bad APIMerge pull request #1573 from ydah/patch-refactorAdd `block_or_numblock_pattern` and replace where usedMerge pull request #1572 from rubocop/rename-pending-to-skip-block-copRename and narrow to `skip` onlyMerge pull request #1566 from ydah/fix/1565Fix edge cases & refactorFix a false positive for `RSpec/PendingWithoutReason` when not inside example and pending/skip with blockMerge pull request #464 from rubocop/match_arrayAdd specs for non-splat case and % literalRely on RESTRICT_ON_SENDMerge pull request #1571 from ydah/suppression-typoAdd settings for typo suppressionPerformance optimizationHandle percent literals as an exceptionModernizeClean up code and add a changelog entryImplement Rubocop::Cop::RSpec::ContainExactly and Rubocop::Cop::RSpec::MatchArrayMerge pull request #1503 from r7kamura/feature/freeze-time-aroundAdd `RSpec/Rails/TravelAround` copAdd `RSpec/RedundantAround` copMerge pull request #1569 from ydah/fix/1149Merge branch 'master' into fix/1149Merge pull request #1564 from ydah/feature/1563Add new `RSpec/PendingBlockInsideExample` copFix a false positive for `RSpec/VariableDefinition` when inside non-spec codeFix a false positive for `RSpec/VariableName` when inside non-spec codeMerge pull request #1558 from ydah/fix-false-positive-rspec-DescribeMethodMerge pull request #1568 from ydah/patch-1Add a link to RSpecExplicitly show that we ignore non-string argumentsFix a false positive for `RSpec/DescribeMethod` when multi-line describe without `#` or `.` at the beginningMerge pull request #1557 from ydah/fix-false-positive-rspec-ContextWordingFix a false positive for `RSpec/ContextWording` when context is interpolated string literal or execute stringDepfu 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