Group react deps together, they fail if not in sync

[silamon]

Proposed change

See #2819

Type of change

• Document existing features within Home Assistant
• Document new or changing features for which there is an existing pull request elsewhere
• Spelling or grammatical corrections, or rewording for improved clarity
• Changes to the backend of this documentation
• Remove stale or deprecated documentation

Checklist

• I have read and followed the documentation guidelines.
• I have verified that my changes render correctly in the documentation.

Additional information

• This PR fixes or closes issue: fixes #
• Link to relevant existing code or pull request:

Summary by CodeRabbit

• Chores
  • Updated dependency management configuration to streamline dependency update processes.

Note: This release contains no user-facing changes. Updates are internal infrastructure improvements.

[coderabbitai]

📝 Walkthrough

Walkthrough

Modified Dependabot configuration to add a new "react" update group for npm packages (react and react-dom) and removed the separate "github-actions" ecosystem update block.

Changes

Cohort / File(s)	Change Summary
Dependabot Configuration .github/dependabot.yml	Added "react" update group under npm ecosystem targeting react and react-dom packages; removed separate github-actions ecosystem block

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description is largely incomplete and does not adequately follow the provided template. While the author included the template structure, they only added a link in the "Proposed change" section without explaining what the changes actually accomplish. All checkboxes in the "Type of change" section remain unchecked, the checklist items are not marked as completed, and the "Additional information" section is empty except for placeholder text. Given that the actual changes involve modifying .github/dependabot.yml to group React dependencies together (per the PR title), the description should have explained this purpose, selected an appropriate change type, and provided relevant context.	The author should update the PR description to fill in the "Proposed change" section with a clear explanation of why React dependencies need to be grouped together in the dependabot configuration and how this change accomplishes that goal. They should select the appropriate "Type of change" checkbox (likely "Changes to the backend of this documentation" or similar), confirm the checklist items, and provide any relevant issue numbers or links. A more complete description will help reviewers understand the motivation and impact of the changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "Group react deps together, they fail if not in sync" directly relates to the main change in the pull request. The raw summary shows that the changes involve adding a new dependabot update group for react and react-dom, which aligns precisely with the title's intent to group these dependencies. The title is concise, specific, and clearly communicates the primary change and rationale to someone reviewing the pull request history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch react

---

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

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/dependabot.yml (1)

1-20: Incomplete PR description.

The PR description is empty—no proposed changes or rationale are documented. While the code change itself is clear from the title and diff, a completed description would help reviewers understand the intent and any edge cases (for example, whether other react-related packages like @types/react or @types/react-dom should also be grouped).

Please fill in the PR description template with details such as the reason for this change, any testing performed, and verification that the dependabot configuration parses correctly.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 39bb544 and b988a78.

📒 Files selected for processing (1)

• .github/dependabot.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Redirect rules - developers-home-assistant
• GitHub Check: Header rules - developers-home-assistant
• GitHub Check: Pages changed - developers-home-assistant

🔇 Additional comments (1)

.github/dependabot.yml (1)

13-16: Approve the react group configuration.

The new "react" group correctly pairs react and react-dom packages to keep their versions in sync during dependency updates. The formatting and indentation are consistent with the existing docusaurus group, and the patterns are appropriate for npm packages.

However, I notice a discrepancy: the AI summary indicates that the github-actions ecosystem block should have been removed, but lines 17–20 show it still present. Please confirm whether the github-actions block was intentionally kept or should be removed as part of this change.

[frenck]

Thanks, @silamon 👍

../Frenck