Remove prConcurrentLimit from renovate config

[mikeallisonJS]

Summary

• Removes the prConcurrentLimit: 2 setting from renovate.json
• Allows renovate to use the default concurrent PR limit from the recommended config
• Simplifies the configuration by removing unnecessary constraint

Testing

• Renovate schema validation (checked in CI)
• Next renovate run will respect the updated configuration
• No code changes; configuration-only update

Summary by CodeRabbit

• Chores
  • Updated dependency management configuration to use recommended settings.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
captainofbass	Ready	Preview, Comment	May 3, 2026 1:56am
mikeallisonjs	Ready	Preview, Comment	May 3, 2026 1:56am
sltdnb	Ready	Preview, Comment	May 3, 2026 1:56am

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: dc720ed7-a59b-4c2a-bd3e-ee7b7c4d17f8

📥 Commits

Reviewing files that changed from the base of the PR and between 0534394 and b3bf741.

📒 Files selected for processing (1)

• renovate.json

---

📝 Walkthrough

Walkthrough

The renovate.json configuration is simplified by removing the explicit prConcurrentLimit: 2 setting and consolidating the extends field to only include the config:recommended preset.

Changes

Renovate Configuration Simplification

Layer / File(s)	Summary
Configuration Update renovate.json	The extends field is simplified to ["config:recommended"], and the prConcurrentLimit: 2 setting is removed, deferring concurrent PR limits to the recommended preset defaults.

---

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

---

Alright, alright, alright! Back to school!

Okay, so here's the thing—this change is like when I finally figured out how to do my homework the easy way. You're basically saying, "Hey, let's just use what Renovate recommends instead of me trying to be some kind of config genius!" Removing that prConcurrentLimit thing and just rolling with the recommended setup? That's a good one!

It's super clean, super simple, and honestly, it shows some real wisdom here. Sometimes you don't need to micromanage every little thing—you just gotta trust the process. Which is what I learned that one time I almost didn't get expelled. Almost!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: removing the prConcurrentLimit setting from renovate.json, which is precisely what the PR does.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/remove-renovatebot-limit

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}