fix(deps): bump parallel to 2.1.0 and rubocop to 1.86.1#173
Merged
Conversation
Dependabot's resolver was crashing because parallel 2.0 was released while rubocop pinned `parallel ~> 1.10`. Rubocop 1.86.1 relaxes that constraint to `>= 1.10`. Closes unhappychoice/oss-issue-opener#146
…llel-crash # Conflicts: # Gemfile.lock
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
1 participant
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.
Summary
parallel1.27.0 → 2.1.0 andrubocop1.86.0 → 1.86.1.Why
Daily Dependabot runs were failing with
Error processing parallel (RuntimeError)because parallel 2.0 was released while rubocop pinnedparallel ~> 1.10. Rubocop 1.86.1 relaxes that to>= 1.10.Test plan
bundle installresolves cleanlyCloses unhappychoice/oss-issue-opener#146
🤖 Generated with Claude Code