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

[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 changes

💡 Result:

Do you want me to look up the official release notes / diff for @types/react v19.2.9 now?

---

🌐 Web query:

DefinitelyTyped React types 19.2.9 release

💡 Result:

Do you want the changelog, release date/publish info, or upgrade/breaking-change notes for @types/react 19.2.9?

---

🌐 Web query:

`@types/react` 19.2.9 breaking changes upgrade notes

💡 Result:

Short summary of breaking / upgrade-relevant TypeScript changes affecting @types/react (React 19 / @types/react ~19.x):

1. Removed deprecated TypeScript types and moved/cleaned up several type definitions — you may see missing legacy types or renamed exports. Run the official codemod to migrate common changes. [1]

2. ReactElement default props type: ReactElement’s default P was changed (now defaults to unknown) — component/JSX prop narrowing and some inferred prop types may require explicit generics or prop typings. [1][2]

3. Refs are made mutable by default (RefObject no longer includes null by default); ref-callback behavior changed (no implicit callback-return typing). Update code that assumes ref types include null or relied on previous callback return semantics. [1][2]

4. Other cleanup: various internal/surface types removed or moved to other packages (some types shifted out of @types/react). Libraries depending on the older @types/react surface may break; update dependent @types packages or pin compatible versions. [1]

Migration actions

• Run the types-react-codemod preset-19 (and the optional react-element-default-any-props codemod if you rely on element.props being any):
  npx types-react-codemod@latest preset-19 ./path-to-app
  npx types-react-codemod@latest react-element-default-any-props ./path-to-your-react-ts-files
  (codemods documented in the React 19 upgrade notes). [1]

• Audit refs and ref callbacks: add explicit nullability where needed (RefObject<T | null>) or update callback signatures per new typings. [1][2]

• Update dependent @types/* packages (or pin @types/react) if third-party typings expect the old types; check DefinitelyTyped issues for packages reporting breakages. [2]

Sources:

• React 19 Upgrade Guide (TypeScript changes & codemods). [1]
• DefinitelyTyped discussion/issues about React 19 types (refs, ReactElement default P, migration notes). [2]

Would you like links to the codemod repo and a short script that runs the recommended codemods across your codebase?

---

🌐 Web query:

`@types/react` 19.2.8 vs 19.2.9 diff patch notes

💡 Result:

Do you want me to look up the exact changes between @types/react 19.2.8 and 19.2.9 (package diff / PRs / changelog)? I can fetch and show the patch notes or commit/PR links.

---

🌐 Web query:

exact package diff PRs changelog `@types/react` 19.2.8 19.2.9

💡 Result:

Short answer: There is no published @types/react 19.2.9 to diff against — the latest published version is 19.2.8 (published ~Jan 10, 2026). See the npm/package listings and DefinitelyTyped repo for the release/commits; to get an exact diff or PR list for 19.2.8, review the types/react commits/PRs in the DefinitelyTyped repo (compare view). [1][2][3]

Sources:

• @types/react package listing (shows v19.2.8 published ~Jan 10, 2026). [1]
• Snyk / package metadata (latest = 19.2.8). [2]
• DefinitelyTyped repository (types/react — use the commits/compare view to see the exact PRs/changes that produced 19.2.8). [3]

If you want, I can:

• produce a precise git commit/PR list and unified diff for the changes that produced 19.2.8 (from the DefinitelyTyped commits), or
• watch for/pull a diff if/when 19.2.9 is published. Which would you prefer?

---

🏁 Script executed:

#!/bin/bash
# Check the package.json in apps/admin for `@types/react` version
cat apps/admin/package.json | jq '.devDependencies["@types/react"]'

# Check if there's a package-lock.json or yarn.lock
if [ -f apps/admin/package-lock.json ]; then
  echo "--- package-lock.json `@types/react` version ---"
  cat apps/admin/package-lock.json | jq '.packages["node_modules/@types/react"].version'
fi

if [ -f apps/admin/yarn.lock ]; then
  echo "--- yarn.lock `@types/react` entry ---"
  grep -A 5 "@types/react@" apps/admin/yarn.lock | head -10
fi

if [ -f apps/admin/pnpm-lock.yaml ]; then
  echo "--- pnpm-lock.yaml exists ---"
  grep -A 3 "@types/react" apps/admin/pnpm-lock.yaml | head -10
fi

Length of output: 65

---

🏁 Script executed:

#!/bin/bash
# Check if `@types/react` 19.2.9 exists on npm registry
echo "=== Checking npm registry for `@types/react`@19.2.9 ==="
npm view `@types/react`@19.2.9 version 2>&1

echo ""
echo "=== Getting latest version of `@types/react` ==="
npm view `@types/react` version 2>&1

echo ""
echo "=== Getting recent versions of `@types/react` ==="
npm view `@types/react` versions --json 2>&1 | jq '.[-10:]'

Length of output: 287

---

🏁 Script executed:

#!/bin/bash
# Get publish date and details for version 19.2.9
echo "=== `@types/react`@19.2.9 publish info ==="
npm view `@types/react`@19.2.9 time

echo ""
echo "=== `@types/react`@19.2.8 publish info ==="
npm view `@types/react`@19.2.8 time

echo ""
echo "=== Checking gitHead (commit hash) for both versions ==="
echo "19.2.8 gitHead:"
npm view `@types/react`@19.2.8 gitHead

echo ""
echo "19.2.9 gitHead:"
npm view `@types/react`@19.2.9 gitHead

Length of output: 56489

---

🌐 Web query:

DefinitelyTyped React types commit January 2026 19.2.8 19.2.9

💡 Result:

• @types/react 19.2.8 — published Jan 10, 2026. [1][2]
• @types/react 19.2.9 — I can’t find a 19.2.9 release or commit in DefinitelyTyped (no published npm release as of Jan 21, 2026). [1][3]

Sources: npm/package metadata and release listings for @types/react and the DefinitelyTyped repo. [1] [2] [3]

References
[1] Socket/npm metadata for @types/react (shows 19.2.8 published Jan 10, 2026).
[2] Snyk package page for @types/react (latest 19.2.8).
[3] DefinitelyTyped repository (types/react) — no 19.2.9 release found.

---

🏁 Script executed:

#!/bin/bash
# Try to get more detailed package information from npm
echo "=== Getting detailed package info for 19.2.9 ==="
npm view `@types/react`@19.2.9 --json 2>&1 | jq '{
  name: .name,
  version: .version,
  description: .description,
  types: .types,
  dependencies: .dependencies,
  publishTime: .time
}'

echo ""
echo "=== Comparing dependencies between versions ==="
echo "19.2.8 dependencies:"
npm view `@types/react`@19.2.8 dependencies 2>&1

echo ""
echo "19.2.9 dependencies:"
npm view `@types/react`@19.2.9 dependencies 2>&1

Length of output: 29921

---

@fingertips18, this dependency update is safe to merge. Here's my analysis:

Summary

This is a patch version update (19.2.8 → 19.2.9) with no breaking changes expected.

Key Findings

Version Details:

• 19.2.8: Published January 10, 2026
• 19.2.9: Published January 20, 2026 (10 days later)
• Dependencies: Both versions have identical dependencies (csstype: ^3.2.2)

Risk Assessment:
✅ Very Low Risk - Here's why:

1. Semantic Versioning: Patch version bumps (the third digit) should only contain:

   • Bug fixes in type definitions
   • Minor type corrections
   • Documentation improvements
   • No breaking changes per semver rules

2. Type-Only Package: Since @types/react is a TypeScript type definition package:

   • It doesn't affect runtime behavior
   • Only impacts TypeScript compilation and type checking
   • Errors would surface during development, not production

3. No Dependency Changes: Both versions use the exact same dependencies, eliminating any transitive dependency risks

4. Established Package: The @types/react package from DefinitelyTyped follows strict semver conventions and has a mature release process

Recommendation

✅ Safe to merge - This is a routine patch update that should cause no issues. The Dependabot PR can be approved and merged confidently.

[dependabot]

Superseded by #856.