chore(deps): update react to v19.2.2

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
react (source)	dependencies	patch	19.2.1 -> 19.2.2
react-dom (source)	dependencies	patch	19.2.1 -> 19.2.2

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[Copilot]

Copilot wasn't able to review any files in this pull request.

[claude]

Pull Request Review

Summary

This is a Renovate Bot automated PR that updates React dependencies from v19.2.1 to v19.2.2 in the documentation site's yarn.lock file.

Review Findings

✅ Approved - Low Risk Change

Code Quality:

• ✅ Clean, automated dependency update
• ✅ Only affects docs/yarn.lock - no source code changes
• ✅ Patch version update (19.2.1 → 19.2.2) indicates bug fixes only

Change Analysis:

• Updates react and react-dom in lockfile
• Version hashes and integrity checksums properly updated
• No breaking changes expected in patch releases

Testing:

• This only affects the documentation site dependencies
• No TUnit core functionality impacted
• Documentation site should be tested after merge to ensure it builds and runs correctly

Security:

• ✅ Patch updates often include security fixes
• React is a well-maintained, trusted dependency
• Integrity checksums present for supply chain security

Performance:

• No performance concerns - patch releases typically include performance improvements or bug fixes

Best Practices:

• ✅ Follows TUnit's dependency management approach
• ✅ Renovate Bot configuration working as expected
• ✅ Automerge is enabled, which is appropriate for low-risk patch updates

Recommendations

1. Verify Documentation Build: After merge, ensure the documentation site builds successfully with the new React versions
2. Monitor for Issues: Watch for any unexpected behavior in the docs site after deployment
3. Consider CI Check: If docs builds aren't part of CI, consider adding them to catch dependency-related build issues early

Conclusion

LGTM - This is a standard, low-risk dependency patch update. The change is isolated to the documentation site's dependencies and should be safe to merge once CI passes.

---

Automated review by Claude Code