chore(deps-dev): bump @types/react-dom from 19.2.2 to 19.2.3 in /apps/frontend

[dependabot]

Bumps @types/react-dom from 19.2.2 to 19.2.3.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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

[fingertips18]

@coderabbitai please confirm that this is good to merge and there are no breaking changes?

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check the package.json in apps/frontend to see the current state
cat apps/frontend/package.json | jq '.dependencies, .devDependencies' | grep -A2 -B2 "react"

Length of output: 1183

---

🏁 Script executed:

#!/bin/bash
# Search for react-dom imports and usage in the frontend app
rg -n --type=ts --type=tsx "from ['\"]react-dom" apps/frontend/src/ 2>/dev/null || rg -n "from ['\"]react-dom" apps/frontend/src/

Length of output: 69

---

🌐 Web query:

@types/react-dom 19.2.3 release notes changelog

💡 Result:

There isn’t a separate formal changelog for @types/react-dom v19.2.3 — the release is the DefinitelyTyped type update that tracks React/React‑DOM changes. See:

• @types/react-dom v19.2.3 release on npm/registry. [1]
• DefinitelyTyped types/react-dom commit history (where the type changes are recorded). [2]
• React 19.2 changelog / release notes (upstream changes that the types follow). [3]

References

1. @types/react-dom releases (npm/registry). [1]
2. DefinitelyTyped — commits for types/react-dom. [2]
3. React 19.2 release notes / changelog. [3]

---

@fingertips18, this PR is safe to merge with no breaking changes expected. Here's my analysis:

✅ Safety Assessment

Version Update: @types/react-dom 19.2.2 → 19.2.3 (patch update)

Key Findings:

1. Patch version only - This is a minor type definitions update that typically includes bug fixes and type improvements
2. Aligned dependencies - Your React dependencies are properly aligned:
   • [email protected] and [email protected] (runtime)
   • @types/[email protected] and @types/[email protected] (type definitions)
3. Minimal usage - Your codebase only imports react-dom/client in apps/frontend/src/main.tsx, which is the standard React 19 pattern
4. No breaking changes - Patch versions of @types packages don't introduce breaking changes; they only refine type definitions to better match the library behavior

Recommendation

✓ Approved for merge - This is a routine type definitions update with no risk to your application functionality.