chore(deps): update dependency parallel to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
parallel (changelog)	"< 2.0" → "< 2.1"

---

Release Notes

grosser/parallel (parallel)

v2.0.1

Compare Source

Added

• require mfa for gem release

v2.0.0

Compare Source

Changed

• Require Ruby >= 3.3
• Add Ruby 4 Ractor support

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[cubic-dev-ai]

1 issue found across 2 files

Confidence score: 3/5

• There is a concrete compatibility risk in Gemfile: allowing parallel 2.0.x conflicts with the stated Ruby 3.2/1.x constraint, which could lead to dependency resolution drift or runtime incompatibilities.
• Given the severity (7/10) and high confidence (9/10), this is more than a housekeeping note and is worth correcting before relying on this change broadly.
• Pay close attention to Gemfile - tighten the parallel upper bound below 2.0 to match the project’s stated compatibility target.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="Gemfile">

<violation number="1" location="Gemfile:17">
P1: This version bound contradicts the stated Ruby 3.2 compatibility constraint by allowing `parallel` 2.0.x. Keep the upper bound below 2.0 if the project must stay on 1.x.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P1: This version bound contradicts the stated Ruby 3.2 compatibility constraint by allowing parallel 2.0.x. Keep the upper bound below 2.0 if the project must stay on 1.x.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At Gemfile, line 17:

<comment>This version bound contradicts the stated Ruby 3.2 compatibility constraint by allowing `parallel` 2.0.x. Keep the upper bound below 2.0 if the project must stay on 1.x.</comment>

<file context>
@@ -14,7 +14,7 @@ gem "rubocop", "~> 1.21"
 
 # parallel 2.0+ requires Ruby >= 3.3; constrain to 1.x to support Ruby 3.2
-gem "parallel", "< 2.0"
+gem "parallel", "< 2.1"
 
 group :development do
</file context>

Suggested change

	gem "parallel", "< 2.1"
	gem "parallel", "< 2.0"

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.