Pin rubocop gems to prevent surprise CI failures#1215
Merged
yukideluxe merged 1 commit intomainfrom Mar 29, 2026
Merged
Conversation
Since Gemfile.lock is not tracked, CI resolves the latest rubocop on every run. Pin rubocop and its extensions to pessimistic patch versions so new cops do not cause surprise failures. Update rubocop_todo for the three new cops introduced in 1.86.0. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
sunny
approved these changes
Mar 29, 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.
@sunny (cc @wwahammy) since Gemfile.lock is not tracked, CI resolves the latest Rubocop on every run. This PR pins Rubocop so CI doesn't inadvertently fails when Rubocop adds news cops 😊
I did not fix the offenses because we do those one by one and I wanted to unlock #1214 first 😊