chore(deps) Update yarn.lock with latest React due to Critical Security Vulnerability 12/3/2025 #40
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Regenerate the yarn.lock file so that it uses the latest React Version to circumvent December 3rd's Critical Security Vulnerability in React Server Components.
This is only a change to our yarn.lock file four our Next.js tests (which use React) because our
package.jsonfile defines thelatestversions of React and Next.js.Note: the placeholder Angular project (which is just a angular init project) didn't like the latest installation of its dependencies, so I pinned their versions for now.