Update Gems and Address New Rubocop Offences #3572
Merged
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
- Commit 02a7cfc bumped the Rubocop version, which resulted in more offences. - These offences should be re-enabled and addressed in the next release.
johnpinto1
approved these changes
Oct 8, 2025
Contributor
johnpinto1
left a comment
johnpinto1
left a comment
There was a problem hiding this comment.
Thanks @aaronskiba for this update.
This was referenced Oct 8, 2025
Open
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.
Changes proposed in this PR:
bundle updateand address resulting Rubocop offencesbundle exec rubocop -Ato autocorrect offences where possibleAdditional Notes
If this PR is merged, then a new issue should be created to ensure that the newly disabled rubocop offences are eventually addressed and then re-enabled.