Update rubocop-performance 1.14.3 → 1.22.1 (minor) - #240
Open
depfu[bot] wants to merge 1 commit into
Open
Conversation
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.
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-performance (1.14.3 → 1.22.1) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
✳️ rubocop (1.50.0 → 1.66.1) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
2.7.2
2.7.1
2.7.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by 44 commits:
v1.26.3Merge pull request #351 from y-yagi/ensure_not_to_use_old_concurrent-rubyEnsure not to use old `concurrent-ruby`v1.26.2Revert "Revert "Merge pull request #348 from y-yagi/use_available_processor_count""v1.26.1Revert "Merge pull request #348 from y-yagi/use_available_processor_count"v1.26.0Merge pull request #348 from y-yagi/use_available_processor_countUse cgroups aware processor count by defaultv1.25.1Merge pull request #347 from Earlopain/speedup-windows-cpuImprove speed for `Get-CimInstance`v1.25.0Merge pull request #346 from Earlopain/drop-win32oleAdd Ruby 3.3 to CIBump `sqlite3` to solve compilation failures with latest libBump `actions/checkout` to v4Remove dependency on `win32ole`Merge pull request #344 from grosser/grosser/readexample for proc usageMerge pull request #343 from grosser/grosser/bumprubocop: fix assignment in conditionupdate rubocopfix rubocopupdate ruby requirementsMerge pull request #341 from MITSUBOSHI/remove-unneeded-travis-envRemove unneeded ENV['TRAVIS'] from specthx for the prv1.24.0Merge pull request #340 from grosser/grosser/orderpolishMerge pull request #339 from shaicoleman/finish-in-orderAdd :finish_in_order optionv1.23.0Merge pull request #336 from grosser/grosser/filter-mapadd filter-mapMerge pull request #333 from M-Yamashita01/fix-inline-method-in-processor-countInline the methods of ProcessorCount module.Merge pull request #331 from msasaki666/add-ruby-3.2-to-ciadd ruby 3.2 to ciMerge pull request #330 from grosser/grosser/docssmall docs fiximprove ractor docsRelease Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
2.9.2 (from changelog)
2.9.1 (from changelog)
2.9.0 (from changelog)
2.8.3 (from changelog)
2.8.2 (from changelog)
2.8.1 (from changelog)
2.8.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 71 commits:
Release v2.9.2Merge pull request #91 from tagliala/security/opt-in-for-mfaOpt-in for MFA requirement explicitlyMerge pull request #92 from tagliala/chore/fix-typosFix typosRelease v2.9.1Unify CHANGELOG formattingSimplify path slightlyMerge pull request #90 from koic/use_require_relativeUse `require_relative` in the Regexp::Parser codebaseRelease v2.9.0Add Ruby 3.3 to build matrixFix b526e4d for ancient rubiesUpdate license yearsFix b526e4d for ancient rubiesAdd support for GCB propertiesAdd `#negative?` to all expressionsRelease v2.8.3Handle leading 0s in group refs, fixes #88Update commentUpdate github actionsRelease v2.8.2Fix rubocopMirror Onigmo quirk for escaped number chains ...Update README.mdTest on 3.2 explicitly, now that head is 3.3Omit docs from bundled gemDeclutter CHANGELOG a bitAdd author in gemspecTest token map against current syntaxRelease v2.8.1Add some missing unicode propertiesSpec https://bugs.ruby-lang.org/issues/19639Update license yearsRelease v2.8.0Run gouteur checks on more recent rubyUpdate comment after b82976bRemove coll. seq. / char. equiv. from scannerCatch \k<0>Define some test methods at class levelFix ivar warningAdd generic #clone/#dup sanity testUse appropriate methodImprove error messageAdd some Token and Expression module aliases ...Fix warning detectionTypoAvoid relying on #token in Expression classesFix Subexpression#te inconsistency with Base#teAssign new #parent when dup-ingFix #full_length for pre-qtf decorationFix 2x dup-ing (same as Shared#initialize_copy)Reduce inspect / pp verbosityAdd integrative spec for #te, #tsFix #to_s with intermittent decorations ...Extract test methods into tests.rbExtract #parts into parts.rbAdd #decorative?, fix comment group qtf parsingMove tests to tests.rb, add specsAdd Expression::Shared#parentSupport 1-arg blocksMove codeUpdate README ...Correction for README after 2.7.0Update .rubocop.ymlExtract scanner errors into files ...Check a bit more consistentlyClean up ragel output a bitFix NoMethodError for #ts on empty seq opFix depth counting for comment groups ...Add #capturing? and #comment? to all expRelease Notes
1.32.3 (from changelog)
1.32.1 (from changelog)
1.32.0 (from changelog)
1.31.3 (from changelog)
1.31.2 (from changelog)
1.31.1 (from changelog)
1.31.0 (from changelog)
1.30.0 (from changelog)
1.29.0 (from changelog)
1.28.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 more commits than we can show here.
Release Notes
2.6.0 (from changelog)
2.5.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 12 commits:
Release v2.6.0Update Unicode version numberUnicode 16.0Update license yearWait for Windows CI to include 3.3README: Update list of supported RubiesUpdate CI Rubies: Add Ruby 3.3Release v2.5.0Update Unicode version numberUnicode 15.1Re-add 3.2 to Windows CIREADME: Update supported Rubies🆕 language_server-protocol (added, 3.17.0.3)
🗑️ rexml (removed)
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.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