Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ruby] Upgrade standard: 0.4.7 → 0.13.0 (major) #204

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Feb 17, 2021

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ standard (0.4.7 → 0.13.0) · Repo · Changelog

Release Notes

0.11.0

  • Update rubocop-performance from 1.9.1 to 1.9.2
  • Update rubocop from 1.4.2 to 1.7.0
  • Changed Style/NegatedIf to postfix

0.10.0

0.6.1

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.

↗️ parser (indirect, 3.0.0.0 → 3.0.1.0) · Repo · Changelog

Release Notes

3.0.1.0 (from changelog)

API modifications:

  • Bump maintenance branches to 3.0.1, 2.7.3, 2.6.7, and 2.5.9 (#791) (Koichi ITO)

Features implemented:

  • Source::TreeRewriter#inspect [#728] (#788) (Marc-André Lafortune)
  • Source::Buffer#inspect [#728] (#787) (Marc-André Lafortune)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 6 commits:

↗️ rubocop (indirect, 0.85.1 → 1.10.0) · 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-performance (indirect, 1.6.1 → 1.9.2) · Repo · Changelog

Release Notes

1.9.2

Bug fixes

  • #201: Fix an incorrect auto-correct for Performance/ReverseEach when using multi-line reverse.each with leading dot. (@koic)

1.9.1

Bug fixes

  • #185: Fix incorrect replacement recommendation for Performance/ChainArrayAllocation. (@fatkodima)

Changes

1.9.0

New features

  • #173: Add new Performance/BlockGivenWithExplicitBlock cop. (@fatkodima)
  • #136: Add new Performance/MethodObjectAsBlock cop. (@fatkodima)
  • #151: Add new Performance/ConstantRegexp cop. (@fatkodima)
  • #175: Add new Performance/ArraySemiInfiniteRangeSlice cop. (@fatkodima)
  • #189: Support auto-correction for Performance/Caller. (@koic)
  • #171: Extend auto-correction support for Performance/Sum. (@koic)
  • #194: Support auto-correction for Performance/UnfreezeString. (@koic)

Changes

  • #181: Change default configuration for Performance/CollectionLiteralInLoop to Enabled: 'pending'. (@ghiculescu)
  • #170: Extend Performance/Sum to register an offense for map { ... }.sum. (@eugeneius)
  • #179: Change Performance/Sum to warn about empty arrays, and not register an offense on empty array literals. (@ghiculescu)
  • #180: Require RuboCop 0.90 or higher. (@koic)

1.8.1

Bug fixes

  • #164: Fix an error for Performance/CollectionLiteralInLoop when a method from Enumerable is called with no receiver. (@eugeneius)
  • #165: Fix a false positive for Performance/Sum when using initial value argument is a variable. (@koic)

Changes

  • #163: Change Performance/Detect to also detect offenses when index 0 or -1 is used instead (ie. detect{ ... }[0]). (@dvandersluis)
  • #168: Extend Performance/Sum to register an offense for inject(&:+). (@eugeneius)

1.8.0

New features

Bug fixes

  • #159: Fix a false positive for Performance/AncestorsInclude when receiver is a variable. (@koic)

Changes

  • #157: Extend Performance/Detect cop with check for filter method and Performance/Count cop with checks for find_all and filter methods. (@fatkodima)
  • #154: Require RuboCop 0.87 or higher. (@koic)

1.7.1

Bug fixes

  • #147: Fix an error for Performance/AncestorsInclude when using ancestors.include? without receiver. (@koic)
  • #150: Fix an incorrect autocorrect for Performance/BigDecimalWithNumericArgument when a precision is specified. (@eugeneius)

Changes

  • #149: Mark Performance/AncestorsInclude as unsafe. (@eugeneius)
  • #145: Mark Performance/StringInclude as SafeAutocorrect: false and disable autocorrect by default. (@koic)

1.7.0

New features

Changes

  • #138: Drop support for RuboCop 0.81 or lower. (@koic)

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.

↗️ unicode-display_width (indirect, 1.7.0 → 2.0.0) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.


Depfu Status

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
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added dependencies Pull requests that update a dependency file depfu labels Feb 17, 2021
@depfu depfu bot force-pushed the depfu/update/standard-0.13.0 branch from 7b05938 to 33751b8 Compare April 29, 2021 04:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file depfu
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants