Update rubocop-minitest 0.35.1 → 0.36.0 (major) #1535
Merged
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-minitest (0.35.1 → 0.36.0) · Repo · Changelog
Release Notes
0.36.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 11 commits:
Cut 0.36.0
Update Changelog
Merge pull request #318 from Earlopain/enable-undefined-config
Merge pull request #317 from Earlopain/multiple-assertions-error
Merge pull request #316 from Earlopain/error-skip-ensure
Enable `InternalAffairs/UndefinedConfig`
Fix an error for `Minitest/MultipleAssertions` when using for-style loops
Fix an error for `Minitest/SkipEnsure` when only `ensure` has a body
Merge pull request #314 from brandoncc/brandoncc/fail-with-usable-message-if-cop-not-defined
Accessing an unregistered cop raises useful error
Switch back docs version to master
✳️ rexml (3.3.6 → 3.3.7) · Repo · Changelog
Release Notes
3.3.7
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 6 commits:
Add 3.3.7 entry
ci document: suppress a ostruct warning
ci document: fix method forwarding with recent Ruby
Remove strscan dependency declaration from gemspec (#204)
Add local entity expansion limit methods (#202)
Bump version
✳️ rubocop (1.65.1 → 1.66.1) · Repo · Changelog
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.
Commits
See the full diff on Github. The new version differs by 10 commits:
v1.26.3
Merge pull request #351 from y-yagi/ensure_not_to_use_old_concurrent-ruby
Ensure not to use old `concurrent-ruby`
v1.26.2
Revert "Revert "Merge pull request #348 from y-yagi/use_available_processor_count""
v1.26.1
Revert "Merge pull request #348 from y-yagi/use_available_processor_count"
v1.26.0
Merge pull request #348 from y-yagi/use_available_processor_count
Use cgroups aware processor count by default
Release Notes
3.3.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:
Update changelog.
Bump version.
* Bump maintenance branches to 3.3.5 (#1039)
Remove `benchmark` dependency from the runner (#1038)
Update changelog.
Bump version.
- Fix errros in the ascii specs of RuboCop (#1037)
Update changelog.
Release Notes
1.32.3 (from changelog)
1.32.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 14 commits:
Cut 1.32.3
Update Changelog
Fix `RuboCop::AST::DefNode#void_context?` to handle class methods called `initialize`
Suppress a Ruby 3.4's obsoleted warning in test
Cut 1.32.2
Optimize forwarded calls
Restore docs/antora.yml
Bump paambaati/codeclimate-action from 8.0.0 to 9.0.0 (#311)
Cut 1.32.1
Update Changelog
Mark `RuboCop::AST::EnsureNode` as being in a void context.
Fix readme CI badge (#308)
Move test `Node#used?` predicate method definition
Restore docs/antora.yml
🗑️ strscan (removed)
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