Remove NeilLuno from Renovate reviewers

[echarrod]

This PR removes NeilLuno from the Renovate reviewers list as he has left the company.

Summary by CodeRabbit

• Chores
  • Updated dependency management configuration to remove one reviewer from the configured reviewer list. The reviewer roster now includes only the remaining nominated reviewers, so future automated reviewer assignments will exclude the removed individual. This change does not affect functionality for end users.

[coderabbitai]

Walkthrough

The pull request updates renovate.json5 by removing "NeilLuno" from the reviewers array. The reviewers array now contains only "echarrod" and "adamhicks". No other configuration values or structure were changed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A twitch of whiskers, name trimmed away,
Two friends remain to check the day.
I nibbled one entry, tidy and bright,
Hop, tap—now the list fits just right. 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between a9c58f0 and 63ba1dc.

📒 Files selected for processing (1)

• renovate.json5 (0 hunks)

💤 Files with no reviewable changes (1)

• renovate.json5

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch remove-neilluno-reviewer

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

renovate.json5 (1)

12-15: Remove stale reviewer references and ensure Renovate config is valid

• We ran ripgrep across the repo and confirmed no occurrences of “NeilLuno” remain.
• The previous npx -y renovate-config-validator invocation failed (package not found). Please validate the Renovate config manually, for example:

  npx -p @renovate/config-validator renovate-config-validator

• Consider switching from individual reviewers to a team-based alias to reduce future maintenance, e.g. in renovate.json5 (lines 12–15):

   "reviewers": [

• "echarrod",
• "adamhicks"

• "team:your-org/renovate-reviewers"
  ]

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**
**Plan: Pro**


<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 9d604d4dda32626993b2dbdd748cdee526b60937 and a9c58f04038f768a5b178109bc03cf4a9d809828.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `renovate.json5` (1 hunks)

</details>

<details>
<summary>🔇 Additional comments (3)</summary><blockquote>

<details>
<summary>renovate.json5 (3)</summary>

`12-15`: **Reviewer removal is correct and scoped as intended**

"NeilLuno" has been removed, leaving the remaining reviewers intact. No other behavioural changes introduced. Looks good.

---

`2-11`: **Quote normalisation and formatting changes are fine**

Switch to double quotes and the tidy-up around general fields look consistent with JSON5 and Renovate expectations. No functional change detected here.

---

`10-11`: **Confirm intended commit message behaviour**

With semanticCommits set to "disabled", Renovate will not generate conventional commit messages and your commitMessagePrefix "renovate:" will be used. Please confirm this is the desired behaviour for your workflows and release tooling.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud