[ruby] Update rubocop-performance 1.25.0 → 1.26.1 (minor) #79
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.25.0 → 1.26.1) · Repo · Changelog
Release Notes
1.26.1
1.26.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 35 commits:
Cut 1.26.1Update ChangelogMerge pull request #521 from Earlopain/disable-bigdecimal[Fix #520] Disable `Performance/BigDecimalWithNumericArgument` by defaultMerge pull request #518 from koic/fix_false_positives_for_performance_redundant_string_chars[Fix #517] Fix false positives for `Performance/RedundantStringChars`Tweak bug report templateSuppress RuboCop's offenseSwitch back docs version to masterCut 1.26.0Update ChangelogFix typosMerge pull request #514 from Earlopain/ci-jrbuy-10Merge pull request #513 from Earlopain/sync-spellcheckingCI against the latest stable JRuby versionRemove misspell from CIRun codespell with `bundle exec rake`Merge pull request #512 from Earlopain/start-end-negationDetect negated conditions with `Performance/DoubleStartEndWith`Merge pull request #511 from rubocop/dependabot/github_actions/actions/checkout-5Bump actions/checkout from 4 to 5Merge pull request #445 from a-lavis/block_given_with_explicit_block_incompatible_with_block_forwardingMerge pull request #504 from lovro-bikic/performance-count-multiline-callFix autocorrection syntax error for Performance/Count with multiline callsMerge pull request #503 from viralpraxis/actualize-referencesActualize referencesMerge pull request #502 from viralpraxis/actualize-performance-sum-cop-reference-uriActualize `Performance/Cop` reference URISuppress RuboCop's warning and offenseMerge pull request #501 from jbpextra/master[Fix rubocop#500] Mark Performance/MapCompact cop as unsafeMerge pull request #498 from viralpraxis/fix-performance-count-cop-error-on-empty-selector-blockFix `Performance/Count` cop error on empty selector blockUse `RuboCop::AST::Node#any_def_type?` methodSwitch back docs version to masterRelease Notes
1.6.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 18 commits:
Merge pull request #3683 from ruby/bump-versionBump to v1.6.0Merge pull request #3679 from Earlopain/parse-as-currentAdd support for `Prism.parse(foo, version: "current")`Merge pull request #3680 from tenderlove/trusted-publishersuse bundler cache instead of bundle installAdd npm publishing workflowAdd crates.io publishing workflowAdd gem publishing workflowMerge pull request #3682 from froydnj/froydnj-unsigned-shift-constantexplicitly cast constants in initializers as wellexplicitly cast shifted constant to unsigned to avoid undefined behaviorMerge pull request #3677 from ruby/dependabot/maven/java-wasm/java-deps-28fddb034aMerge pull request #3678 from ruby/dependabot/bundler/gemfiles/typecheck/ruby-deps-d1823ef2f3Bump sorbetBump the java-deps group in /java-wasm with 3 updatesMerge pull request #3676 from bugtender/fix-broken-links-in-design-docFix broken tdop links in docs/design.mdDepfu 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