chore(deps-dev): bump @types/react from 19.2.8 to 19.2.9 in /apps/frontend

[dependabot]

Bumps @types/react from 19.2.8 to 19.2.9.

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)

[fingertips18]

@coderabbitai Are there any breaking changes in this dependency update? Is it safe to merge?

[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.}

[coderabbitai]

Tip

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

🧩 Analysis chain

🌐 Web query:

`@types/react` 19.2.9 changelog release notes

💡 Result:

I couldn't find a @types/react 19.2.9 release. The @types/react release listings show up through 19.2.8 / 19.2.3 in public trackers; no 19.2.9 entry appears in the npm/release lists I checked. [1][2]

If you want, I can:

• keep checking and notify you if 19.2.9 appears, or
• fetch the changelog for the latest published 19.2.x version instead.

Sources:
[1] @types/react release listing (release tracker).
[2] Snyk package info showing latest listed @types/react versions (up through 19.2.8).

---

🏁 Script executed:

#!/bin/bash
# Check the package.json changes in this PR
git diff origin/main HEAD -- apps/frontend/package.json

# Check if there's a package-lock.json or yarn.lock with more details
git diff origin/main HEAD -- apps/frontend/package-lock.json | head -100

Length of output: 4353

---

🌐 Web query:

DefinitelyTyped react 19.2.9 commit changes github

💡 Result:

The DefinitelyTyped commit that introduced the React 19.2 changes is commit a8df5b8 ("[react] 19.2") in the DefinitelyTyped repo; see the commit history for types/react on GitHub. (github.com)

The @types/react package latest published version is 19.2.9 (npm/Snyk listing); for the exact per-PR/commit changes that produced 19.2.9, inspect the types/react commit history and the individual PRs linked there. (security.snyk.io)

Would you like me to list the individual PRs/changes included in 19.2.x (or extract the diffs for 19.2.9)?

Citations:

• 1: DefinitelyTyped/DefinitelyTyped@a8df5b8
• 2: https://security.snyk.io/package/npm/%40types%2Freact/19.0.2?utm_source=openai

---

🏁 Script executed:

#!/bin/bash
# Check the DefinitelyTyped repository for recent commits to types/react
# We'll look at the commit history to see what changed between 19.2.8 and 19.2.9

# First, let's check if there are any other files in the PR that might give us clues
git log --oneline -10 --all -- apps/frontend/package.json

# Check the current React version being used
cat apps/frontend/package.json | grep -A 2 -B 2 '"react"'

Length of output: 850

---

@fingertips18: Yes, this is safe to merge. Here's why:

✅ No Breaking Changes Expected

• This is a patch version update (19.2.8 → 19.2.9) in type definitions
• Patch versions follow semantic versioning and don't introduce breaking changes
• The @types/react package only provides TypeScript type definitions, not runtime code

✅ Compatibility

• Your project uses React 19.2.0, which aligns perfectly with these type definitions
• The only dependency (csstype@^3.2.2) remains unchanged
• Package lock changes show only integrity hash updates and minor optimizations

✅ Low Risk

• Type definition updates refine or fix types without affecting runtime behavior
• Dependabot's compatibility score indicates this is a safe update
• This follows the normal pattern of your other dependency updates

Recommendation: Merge after CI passes. Type definition patch updates are among the safest dependency updates you can make.

[dependabot]

Superseded by #857.