chore(deps): update dependency @testing-library/react to v16.3.2

[WomB0ComB0]

This PR contains the following updates:

Package	Change	Age	Confidence
@testing-library/react	16.3.1 → 16.3.2

---

Release Notes

testing-library/react-testing-library (@​testing-library/react)

v16.3.2

Compare Source

Bug Fixes

• Update 'onCaughtError' type inference in 'RenderOptions' to work with React v19 (#​1438) (f32bd1b)

---

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 this update again.

---

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

---

This PR has been generated by Renovate Bot.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
portfolio	Error		Jan 20, 2026 7:38am

[gemini-code-assist]

Summary of Changes

Hello @WomB0ComB0, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates the update of the @testing-library/react dependency to its latest patch version. The primary goal is to incorporate a specific bug fix related to type inference for React v19, ensuring continued compatibility and stability within the testing environment. This keeps the project's testing infrastructure current with the latest improvements and prepares for future React versions.

Highlights

• Dependency Update: The @testing-library/react dependency has been updated from version 16.3.1 to 16.3.2.
• Bug Fix: This update includes a bug fix to improve onCaughtError type inference in RenderOptions for compatibility with React v19.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

📝 Walkthrough

Walkthrough

The @testing-library/react development dependency version is updated from 16.3.1 to 16.3.2 in package.json. This is a patch-level version bump with no functional or control-flow changes.

Changes

Cohort / File(s)	Change Summary
Dependency Update package.json	@testing-library/react dev dependency bumped from 16.3.1 to 16.3.2

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

released

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: updating @testing-library/react to v16.3.2, which is the sole purpose of this PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

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

[gemini-code-assist]

Code Review

This pull request updates the @testing-library/react dependency to version 16.3.2. This is a patch release that includes a bug fix for compatibility with React 19, which this project uses. The change is correct and safe to merge. I have included one suggestion to improve the consistency of dependency versioning within your package.json for better long-term maintainability.

[gemini-code-assist]

I've noticed an inconsistency in how dependency versions are specified in package.json. Some testing libraries like vitest and @playwright/test use caret ranges (^), while the @testing-library/* packages are pinned. To improve consistency and simplify future updates, consider using a caret range here. A follow-up change to align the other @testing-library packages would also be beneficial.

Suggested change

	"@testing-library/react": "16.3.2",
	"@testing-library/react": "^16.3.2",