Update rubocop-rspec 3.0.1 → 3.0.2 (patch) #220
Closed
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}
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 (3.0.1 → 3.0.2) · Repo · Changelog
Release Notes
3.0.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
Merge pull request #1933 from rubocop/releaseRelease v3.0.2Merge pull request #1931 from jeppester/masterBetter assist rspec rails cop users when migrating to 3Merge pull request #1930 from Earlopain/false-negative-predicate-matcherFix false negative for `RSpec/PredicateMatcher` when expectation contains custom failure messageMerge pull request #1927 from bmulholland/patch-1Apply suggestions from code reviewchore(docs): Gem names and troubleshooting for v3 migration instructionsMerge pull request #1924 from rubocop/add-tocAdd table of contents in READMEMerge pull request #1923 from rubocop/ydah-patch-1Add link to "Upgrade to Version 3.x" in READMEMerge pull request #1918 from Earlopain/invalid-autocorrect-scattered-setup[Fix #1913] Fix broken autocorrect for `RSpec/ScatteredSetup` when block contains heredocMerge pull request #1922 from rubocop/ydah-patch-1Fix to upgrade_to_version_3.adocRelease Notes
3.3.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 13 commits:
Add 3.3.1 entryOptimize BaseParser#unnormalize method (#158)Reuse of Set.new at prefixes variables (#157)Add changelog_uri to gemspec (#156)Don't include private_constant-ed module (#155)Fix a bug that a large XML can't be parsed (#154)Reject unclosed DOCTYPE on parsing (#153)Add a "Malformed comment" check for invalid comments such as `<!-->` (#147)Fix small typos (#148)Improve `Element#attribute` implementation as 6500x faster (#146)Add a "malformed comment" check for top-level comments (#145)Remove an unused class var `@@namespaces` (#144)Bump versionDepfu 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