chore: sync rbs collection lock (prism 1.6.0 -> 1.7.0)#683
Merged
Conversation
aguspe
force-pushed
the
chore/rbs-collection-prism-update
branch
from
4c57af6 to
3a2e4dd
Compare
aguspe
force-pushed
the
chore/rbs-collection-prism-update
branch
from
3a2e4dd to
71f7602
Compare
KazuCocoa
approved these changes
Jun 7, 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
2 participants
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.
Re-ran
rbs collection updateso the locked RBS versions match Gemfile.lock — prism was pinned at 1.6.0 while we resolve 1.7.0, which made steep warn on every run.No code or type-check changes; unit tests stay green.