Skip to content

Update standard 1.49.0 → 1.50.0 (minor) #53

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
May 17, 2025
Merged

Update standard 1.49.0 → 1.50.0 (minor) #53

merged 1 commit into from
May 17, 2025

Conversation

depfu[bot]
Copy link

@depfu depfu bot commented May 14, 2025

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?

✳️ standard (1.49.0 → 1.50.0) · Repo · Changelog

Release Notes

1.50.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 3 commits:

↗️ json (indirect, 2.10.2 → 2.12.0) · Repo · Changelog

Release Notes

2.12.0 (from changelog)

  • Improve floating point generation to not use scientific notation as much.
  • Include line and column in parser errors. Both in the message and as exception attributes.
  • Handle non-string hash keys with broken to_s implementations.
  • JSON.generate now uses SSE2 (x86) or NEON (arm64) instructions when available to escape strings.

2.11.3 (from changelog)

  • Fix a regression in JSON.pretty_generate that could cause indentation to be off once some #to_json has been called.

2.11.2 (from changelog)

  • Add back JSON::PRETTY_STATE_PROTOTYPE. This constant was private API but is used by popular gems like multi_json. It now emits a deprecation warning.

2.11.1

What's Changed

  • Add back JSON.restore, JSON.unparse, JSON.fast_unparse and JSON.pretty_unparse.
    These were deprecated 16 years ago, but never emited warnings, only undocumented, so are
    still used by a few gems.

Full Changelog: v2.11.0...v2.11.1

2.11.0

What's Changed

  • Optimize Integer generation to be ~1.8x faster.
  • Optimize Float generation to be ~10x faster.
  • Fix JSON.load proc argument to substitute the parsed object with the return value.
    This better match Marshal.load behavior.
  • Deprecate JSON.fast_generate (it's not any faster, so pointless).
  • Deprecate JSON.load_default_options.
  • Deprecate JSON.unsafe_load_default_options.
  • Deprecate JSON.dump_default_options.
  • Deprecate Kernel#j
  • Deprecate Kernel#jj
  • Remove outdated JSON.iconv.
  • Remove Class#json_creatable? monkey patch.
  • Remove deprecated JSON.restore method.
  • Remove deprecated JSON.unparse method.
  • Remove deprecated JSON.fast_unparse method.
  • Remove deprecated JSON.pretty_unparse method.
  • Remove deprecated JSON::UnparserError constant.
  • Remove outdated JSON::MissingUnicodeSupport constant.

Full Changelog: v2.10.2...v2.11.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.

↗️ language_server-protocol (indirect, 3.17.0.4 → 3.17.0.5) · Repo · Changelog

Release Notes

3.17.0.5 (from changelog)

  • Use JSON.generate() instead to improve performance (#115)

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

Commits

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

↗️ parallel (indirect, 1.26.3 → 1.27.0) · Repo

Commits

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

↗️ parser (indirect, 3.3.7.4 → 3.3.8.0) · Repo · Changelog

Release Notes

3.3.8.0 (from changelog)

API modifications:

  • Bump maintenance branches to 3.3.8 (#1077) (Koichi ITO)
  • YARD docs for Parser::CurrentRuby and Parser::Base#version (#1076) (Vince Broz)

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

Commits

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

↗️ rubocop (indirect, 1.75.2 → 1.75.5) · Repo · Changelog

Release Notes

1.75.5

Bug fixes

  • #14148: Fix an infinite loop error for Layout/SpaceAfterSemicolon with Layout/SpaceBeforeSemicolon when a sequence of semicolons appears. (@koic)
  • #14145: Fix Lint/ArrayLiteralInRegexp cop error on empty interpolation. (@viralpraxis)
  • #14072: Fix autocorrect issue in Layout/HashAlignment. (@jonas054)
  • #14131: Fix false positives for Style/ArgumentsForwarding when using anonymous block argument forwarding to a method with a block. (@koic)
  • #14140: Fix Layout/LeadingCommentSpace to allow splitting long inline RBS comment signatures across multiple lines. (@Morriar)
  • #14147: Fix Lint/LiteralAsCondition cop error on if without body. (@viralpraxis)
  • #14151: Fix Lint/Void cop error on nested empty begin. (@viralpraxis)
  • #13547: Fix Style/IdenticalConditionalBranches cop failure in case of if node with implicit then. (@viralpraxis)
  • #14146: Fix Style/MethodCallWithArgsParentheses cop error on complex numbers when EnforcedStyle is set to omit_parentheses. (@viralpraxis)
  • #14137: Fix Style/TrailingCommaInArguments cop error if EnforcedStyleForMultiline is set to comma. (@viralpraxis)

Changes

  • #14144: Layout/SpaceInsideArrayLiteralBrackets make aware of array pattern matching. (@koic)
  • #14142: Layout/SpaceInsideHashLiteralBraces make aware of hash pattern matching. (@koic)

1.75.4

Bug fixes

  • #14123: Fix an infinite loop error for Lint/BooleanSymbol when using the rocket hash syntax with a boolean symbol key. (@koic)
  • #14134: Fix an error for Style/ComparableBetween when comparing the value with itself. (@earlopain)
  • #14111: Fix an error for Style/SafeNavigation when the RHS of && is a complex || expression composed of && conditions. (@koic)
  • #14129: Fix false positives for Style/ArgumentsForwarding when using default positional arg, keyword arg, and block arg in Ruby 3.1. (@koic)
  • #14110: Fix false positives for Style/RedundantParentheses when parens around basic conditional as the second argument of a parenthesized method call. (@koic)
  • #14120: Fix false positives for Style/RedundantParentheses when parens around unparenthesized method call as the second argument of a parenthesized method call. (@koic)
  • #14133: Fix Lint/LiteralAsCondition autocorrect when a literal is the condition of an elsif followed by an else. (@zopolis4)
  • #14116: Make Style/TrailingCommaInArguments cop aware of trailing commas in [] method call. (@viralpraxis)
  • #14114: Fix Style/ClassAndModuleChildren cop error on tab-intended compactable modules. (@viralpraxis)

Changes

1.75.3

Bug fixes

  • #13676: Allow RuboCop to inspect hidden directories if they are explicitly provided. (@viralpraxis)
  • #14080: Allow writing RBS::Inline annotation #: after end keyword in Style/CommentedKeyword. (@dak2)
  • #14075: Fix an error for Layout/EmptyLineAfterGuardClause when calling a method on the result of a single-line if with return. (@koic)
  • #14067: Fix false negatives for Style/RedundantParentheses when using parens around singleton method body. (@koic)
  • #14070: Fix false positives for EnforcedStyleForMultiline: diff_comma of Style/TrailingCommaInArrayLiteral and Style/TrailingCommaInHashLiteral when trailing comma with comment. (@koic)
  • #14092: Fix false negative for Style/RedundantParentheses when using some operator methods with a parenthesized argument. (@koic)
  • #14103: Fix Layout/MultilineOperationIndentation cop error on indexasgn node without arguments. (@viralpraxis)
  • #14089: Fix redundant current directory prefix regexp. (@sferik)
  • #14099: Fix Style/ClassAndModuleChildren cop error on one-liner class definition and nested enforced style. (@viralpraxis)
  • #14083: Fix Style/ConditionalAssignment cop error on one-line if-then-else. (@viralpraxis)
  • #14104: Fix Style/ConditionalAssignment cop error on indexed assignment without arguments. (@viralpraxis)
  • #14084: Fix Style/RedundantLineContinuation cop error on multiline assignment with line continuation. (@viralpraxis)
  • #14096: Fix error for Style/SafeNavigation with longer && chain (e.g. a && a.b && a.b.c). (@lovro-bikic)
  • #14068: Fix wrong autocorrection for Style/MapIntoArray when using push or append with hash argument without braces. (@lovro-bikic)

Changes

  • #14093: Register offenses for redundant parens around method arguments for Style/RedundantParentheses. (@lovro-bikic)
  • #14064: Prefer References over Reference in cop configs. (@sambostock)

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.

↗️ rubocop-ast (indirect, 1.44.0 → 1.44.1) · Repo · Changelog

Release Notes

1.44.1

Bug fixes

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

Commits

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

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 cancel merge
Cancels automatic merging of this PR
@​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 the depfu label May 14, 2025
@pboling pboling merged commit b9866a3 into main May 17, 2025
3 of 7 checks passed
@depfu depfu bot deleted the depfu/update/standard-1.50.0 branch May 17, 2025 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
depfu
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@pboling