Update standard 1.40.0 → 1.41.1 (minor) #6
Closed
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?
✳️ standard (1.40.0 → 1.41.1) · Repo · Changelog
Release Notes
1.41.1 (from changelog)
1.41.0 (from changelog)
1.40.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 10 commits:
1.41.1
Merge pull request #655 from vinistock/vs-add-range-formatting-method
Add range formatting method to the formatter add-on
🐙 v1.41.0
Merge pull request #653 from standardrb/updates-2024-10-08
Updates rubocop and standard-performance, handles new cops
1.40.1
Fix embarassment of issues
Merge pull request #651 from spencern/patch-1
Add Privy to Standard users list
Release Notes
3.3.8
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
test: avoid using needless non ASCII characters
Add 3.3.8 entry
Fix handling with "xml:" prefixed namespace (#208)
Optimize SAX2Parser#get_namespace (#207)
Bump version
Release Notes
1.66.1
1.66.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.
Release Notes
1.22.1
1.22.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 26 commits:
Cut 1.22.1
Update Changelog
Merge pull request #469 from koic/fix_false_positives_for_performance_big_decimal_with_numeric_argument_cop
[Fix #468] Fix false positives for `Performance/BigDecimalWithNumericArgument`
Switch back docs version to master
Cut 1.22.0
Update Changelog
Merge pull request #465 from Earlopain/start-end-safe-navigation
[Fix #407] Make `Performance/DoubleStartEndWith` aware of safe navigation
Merge pull request #466 from Earlopain/block-given-disable
[Fix #385] Disable `Performance/BlockGivenWithExplicitBlock` by default
Add changelog entry for #463
Merge pull request #463 from koic/fix_false_positives_for_performance_big_decimal_with_numeric_argument
[Fix #454] Fix false positives for `Performance/BigDecimalWithNumericArgument`
Merge pull request #459 from Earlopain/rubocop-workaround
Merge pull request #460 from Earlopain/enable-undefined-config
Enable `InternalAffairs/UndefinedConfig`
Remove RuboCop < 1.44 workaround
Merge pull request #458 from Earlopain/flaky-autocorrect-specs
Fix a random test failure for `Performance/Sum`
Merge pull request #457 from Earlopain/cop-registry-deprecated
Don't use deprecated `Cop.registry` in specs
Suppress RuboCop offenses
Suppress RuboCop offense
Use RuboCop RSpec 3.0
Switch back docs version to master
Release Notes
1.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 8 commits:
👩💻 v1.5.0
Merge pull request #27 from standardrb/updates-08-10-2024
Updates Rubocop Performance to 1.22.1
Merge pull request #26 from mjankowski/ruby-eol-ci
Restore 3.0 to CI, bump gemspec
Remove conditional Ruby 2.7 checks
Drop EOL ruby from CI config
Update `actions/checkout` to v4 (node 16->20)
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