[ruby] Update rubocop-rspec 2.28.0 → 2.29.1 (minor) #64
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
digitaltom
force-pushed
the
main
branch
2 times, most recently
from
40d4c02 to
ed2de35
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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-rspec (2.28.0 → 2.29.1) · Repo · Changelog
Release Notes
2.29.1
2.29.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 27 commits:
Merge pull request #1863 from rubocop/releaseBump to v2.29.1Merge pull request #1862 from rubocop/improve-release-notes-workflowSwitch docs version backMerge pull request #1861 from rubocop/followWhen creating a release, automatically add a titleAdd VersionAdd for `RSpec/EmptyOutput`Merge pull request #1860 from rubocop/releaseBump to v2.29.0Merge pull request #1854 from rubocop/empty-outputMerge pull request #1859 from rubocop/automatically-create-release-notesCreate GH release with notes on CI gem publishingMerge pull request #1829 from rubocop/trusted-publishingUse Rubygems Trusted Publishers to publishAdd new RSpec/EmptyOutput copMerge pull request #1796 from rubocop/add-xstr-onlyAdd new `RSpec/UndescriptiveLiterals` copMerge pull request #1856 from rubocop/expect-actual-autocorrect-with-hashFix #1834 autocorrect error for RSpec/ExpectActualMerge pull request #1855 from rubocop/fix-flakyFix a flaky test for spec/project/default_config_spec.rbMerge pull request #1853 from rubocop/fix-comment-indentationsFix indentation of some commentsMerge pull request #1851 from rubocop/fix-invalid-commentFix a invalid base class comment for rubocop-rspec_railsMerge pull request #1845 from rubocop/switch-docsSwitch docs version backRelease Notes
2.7.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 21 commits:
Bump up 2.7.2Merge pull request #578 from flori/warn-bundled-gemsWarn to install ostruct if json couldn't load itMerge pull request #577 from tompng/autoload_generic_objectMerge pull request #576 from headius/no_19_jruby_methodsAutoload GenericObject to avoid require ostruct warning in Ruby 3.4Remove references to "19" methods in JRubyMerge pull request #575 from flori/refine-ciExclude 2.3-2.5 on macos-14 iamgeAdded JRuby 9.4TruffleRuby 24 is brokenAdded latest stable versions of macOSmacOS 11 is EOL todayMerge pull request #574 from peterzhu2118/generator-mem-leakFix memory leak when exception is raised during JSON generationMerge pull request #571 from mperham/patch-1Update README.mdMerge pull request #565 from flori/optional-ostructMake OpenStruct support as optionalMerge pull request #561 from jhawthorn/rb_sym2strUse rb_sym2str instead of SYM2IDDepfu 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