chore: Lock RuboCop at 1.90 for CI stability - #527
Merged
Merged
Conversation
arjun-rajappa
force-pushed
the
pin-rubocop-version
branch
from
September 15, 2026 09:13
c7f7df5 to
8f18603
Compare
Signed-off-by: Arjun Rajappa <arjun.rajappa@ibm.com>
arjun-rajappa
force-pushed
the
pin-rubocop-version
branch
from
September 15, 2026 09:31
8f18603 to
eef5dd0
Compare
|
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.
We should pin RuboCop to a specific version to avoid continuous master build failures. Currently, new RuboCop releases introduce rule changes that break our pipeline. Pinning the version will ensure stability. Lint to the latest failure - circle-ci