[ruby] Update Gem Dependencies#107
Merged
Merged
Conversation
de5de77 to
b0dacc4
Compare
This was referenced Jun 20, 2026
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
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.
1. Overview
This PR (#107) updates the Gem dependencies of the
ruby/project in thecoding-testsrepository.It is a small, focused update that bumps a single directly declared gem (
rubocop) inGemfileand one transitively locked gem (rbs) inGemfile.lock.Both are in-major-version bumps, so no breaking changes are expected.
2. Key Changes & Differences in Each Gem
ruby/Gemfile(gem 'rubocop', '~> 1.88.0'). Minor bump adding new cops and bug fixes.rbs-inline/steep. Patch release.3. Summary
This is a minimal maintenance update.
The only directly requested change is
rubocop1.86.2 → 1.88.0, withrbs4.0.3 resolved transitively by Bundler.The other RuboCop plugins (
rubocop-minitest,rubocop-performance) andsteepwere left untouched and remain compatible with the new RuboCop version.The change is confined to the development/lint/type-checking toolchain and carries minimal risk.
4. References